---
title: "corestack_deployments_variable_reveal"
url: https://docs.corefinity.com/mcp/tools/corestack_deployments_variable_reveal
type: tool
last_updated: 2026-11-13
feature: deployment-variables
related:
  - https://docs.corefinity.com/api/reference/deployments/reveal-site-deployment-variable.md
  - https://docs.corefinity.com/guides/sites/code-and-deployments/variables-and-secrets.md
---
# corestack_deployments_variable_reveal

**Show a deployment variable.** Show the value of one of the environment's deployment variables — in the person's browser by default. The reveal is recorded. Scope: exec. The secret opens in the person's browser; set reveal_to_agent to true to receive it yourself (needs exec).

- Scope: `exec`
- Runs as a task: no
- Returns a secret only when `reveal_to_agent` is set

## When to use it

Show the value of one of the environment's deployment variables. By default it opens in the person's browser on a secret page, and nothing is read until they press Show. Only with exec and `reveal_to_agent: true` is the value returned to you. The reveal is recorded. This is the only way a stored value is shown: the variables list never carries one.

The same action in the public REST API, with the same checks, refusals and scope: `POST /api/corestack/sites/{site}/deployments/variables/{name}/reveal`. It answers the value to the token's own user, as `reveal_to_agent` does here.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `name` (string, matching `^[A-Za-z_][A-Za-z0-9_]{0,63}$`, required): The variable's name from corestack_deployments_variables_list.
- `reveal_to_agent` (boolean, default `false`): Return the secret to you instead of opening it in the person's browser. Needs exec.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "name": {
      "description": "The variable's name from corestack_deployments_variables_list.",
      "pattern": "^[A-Za-z_][A-Za-z0-9_]{0,63}$",
      "type": "string"
    },
    "reveal_to_agent": {
      "default": false,
      "description": "Return the secret to you instead of opening it in the person's browser. Needs exec.",
      "type": "boolean"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "name"
  ],
  "type": "object"
}
```

## Refusals

- `not_available`: the stored value cannot be read; save it again with corestack_deployments_variable_set.
- `managed_elsewhere` (message: "This site is managed by another control panel"): 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.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_deployments_variable_reveal",
  "arguments": {
    "site_id": 4211,
    "name": "API_TOKEN"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_deployments_variable_reveal with site_id 4211, name API_TOKEN. (Show a deployment variable.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/deployments/variables/{name}/reveal](https://docs.corefinity.com/api/reference/deployments/reveal-site-deployment-variable.md)
- Guide: [Variables](https://docs.corefinity.com/guides/sites/code-and-deployments/variables-and-secrets.md)
