corestack_ external_ db_ get
Database tab.
When to use it
Read an environment's Database tab: how to connect, its database users and its external database access. Use it before adding, changing or removing a database user, and to find the host, port and allowed addresses an outside system needs.
connectionis how the site's own tools reach the database: host127.0.0.1, port 3306, the database, and the SSH tunnel command for a client outside the environment. It never holds a login.usersstarts withapplication, the site's own login (kind: protected); its password is shown bycorestack_db_credentials_get, and it is never changed here. The rest are the users added on this environment:internalones connect from inside the site (its crons, the terminal and the SSH tunnel),externalones through external access from the allowed addresses only. Each says its access (read_onlyorread_write), its limits, whether it requires TLS, who added it and when, and whether a change to it is still applying (pending).countssays how many users the environment has and the caps: 10 users, at most 5 of them external.externalis external database access: its status (off,turning_on,tonightwhile the first turn-on waits for the nightly window named bywindow_date,on,failed,turning_off), whether this environment can take it (available), the host (null until the first turn-on) and port outside systems connect to, the allowed addresses and the monthly price.moved_atsays when a move of the environment turned access on again: the address changed then, so outside systems must use the new one. It is null while external access is not available to the person.cansays what the person may do here.
Ask for it
Using the Corefinity MCP server, call corestack_external_db_get with site_id 4211. (Database tab.) Tell me what it returned.Inputs
site_idintegerRequired
The environment's row: the site (its production) or one of its environments. At least 1.
Example call
{
"name": "corestack_external_db_get",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
The same task elsewhere
Was this helpful?