corestack_ deployments_ variables_ list
Deployment variables.
When to use it
The environment's CF_ deployment variables: names, masks, log visibility and the stages whose lines use them. Never a value.
A variable named as a build tool's credential (COMPOSER_AUTH, NPM_TOKEN, NODE_AUTH_TOKEN, YARN_NPM_AUTH_TOKEN, GITHUB_TOKEN, GITLAB_TOKEN, BITBUCKET_TOKEN) that no stage reads as $CF_<name> carries tool_credential, a sentence to show the person: builds see it as CF_<name>, so the tool never reads it, and the credentials belong under Private registries (corestack_deployments_secret_set). It is null for every other variable. New variables of those names are refused.
The same action in the public REST API, with the same checks, refusals and scope: GET /.
Ask for it
Using the Corefinity MCP server, call corestack_deployments_variables_list with site_id 4211. (Deployment variables.) Tell me what it returned.Inputs
At least 1.
Example call
{
"name": "corestack_deployments_variables_list",
"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. |