corestack_ external_ db_ disable
Turn off external database access.
When to use it
Turn off external database access for an environment. Its external users are removed at once, so nobody can sign in from outside from that moment; the monthly charge stops from now; then the public endpoint, the host name's record and the fixed address go. Internal users keep working.
The address cannot be got back: turning access on again later gives a new address under the same host name, and every outside system must then connect to it. Ask the person to type the environment's name, and send it as confirm_environment (as the site shows it, for example Production). Turning it off needs the site's billing rights.
Ask for it
Using the Corefinity MCP server, call corestack_external_db_disable with site_id 4211. (Turn off external database access.) Tell me what it returned.Inputs
The environment's name, typed, e.g. Production. Up to 191 characters.
At least 1.
Your assistant fills in a confirmation only after you agree.
Example call
{
"name": "corestack_external_db_disable",
"arguments": {
"site_id": 4211,
"confirm_environment": "Production"
}
}If it is refused
| Reason | What to do |
|---|---|
confirm_mismatch | confirm_environment is not the environment's name; nothing changed. |
billing_forbidden | The person cannot change this site's billing; the site's owner turns it off. |
external_db_already_off | External access is off already (or turning off). |
external_db_failed | The last change to external access failed; Corefinity support retries or releases it. |
busy | Another change to this environment is applying. |
deleted | The site is deleted (in its grace period). |
provisioning | The site is still being created. |
managed_elsewhere | Another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done. |
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. |