---
title: "corestack_enterprise_variables_list"
url: https://docs.corefinity.com/mcp/tools/corestack_enterprise_variables_list
type: tool
last_updated: 2026-11-13
feature: enterprise-variables
related:
  - https://docs.corefinity.com/guides/corestack-enterprise/environment-variables.md
---
# corestack_enterprise_variables_list

**CoreStack Enterprise build variables.** A CoreStack Enterprise environment's build variables, which its deployments receive as CF_<name>: names, masked values and the stages that read them. Never a value. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

Read a CoreStack Enterprise environment's build variables, as its environment page's Environment Variables editor keeps
them: every deployment of the environment receives each one as `CF_<name>`. Each variable comes with its `name`, its
`masked` value (the mask, and the last four characters of a value of 16 characters or more), `used_in` (the pipeline
stages whose commands read `$CF_<name>`; empty when none does), `replaces_platform`, `tool_credential` and `updated_at`.
The answer also gives `count` and `limit`, the most variables the environment can hold.

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. It is null for every other
variable.

It never carries a value, not even for a variable once marked to be shown in deployment output (one kept from when the
environment ran a CoreStack site): that one is masked too. `corestack_enterprise_variable_reveal` shows a value. For a
CoreStack or CoreCluster site, use `corestack_deployments_variables_list` by `site_id` instead.

The public API's `GET /api/environments/{environment}/variables` answers the same.

## Inputs

- `enterprise_env_id` (integer, ≥ 1, required)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "enterprise_env_id": {
      "description": "A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "enterprise_env_id"
  ],
  "type": "object"
}
```

## Refusals

- `invalid_arguments` (field `enterprise_env_id`): a CoreStack or CoreCluster environment; use the
  `corestack_deployments_*` tools by `site_id`.
- `tenant_mismatch` (also for an environment hidden from the person), `pin_refused`, and the refusals every tool can
  answer: `scope_required`, `rate_limited`, `temporarily_unavailable`, `internal_error`
  (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_enterprise_variables_list",
  "arguments": {
    "enterprise_env_id": 1530
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_enterprise_variables_list with enterprise_env_id 1530. (CoreStack Enterprise build variables.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Environment variables](https://docs.corefinity.com/guides/corestack-enterprise/environment-variables.md)
