environments_promote
Run environments.promote through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/environments-promote.md
What environments_promote does on Appaloft
AI agents invoke environments_promote to trigger actions in Appaloft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
targetKind | string | Yes | |
targetName | string | Yes | |
environmentId | string | Yes |
Parameters from the server's own tool schema.
Why environments_promote is rated High
Promoting an environment typically triggers a deployment or configuration change pipeline, which is an external operation with significant side effects. It doesn't clearly delete data (so not Destructive) nor move money (not Financial), but it executes a potentially irreversible infrastructure operation. Severity is high because promoting to production can affect live users and systems at scale.
From the tool's definition 'Run environments.promote through the Appaloft application operation catalog' — uses 'Run' indicating execution of an operation; 'promote' suggests moving an environment between stages (e.g., staging to production).
Attacks that exploit this kind of access
The rule that runs environments_promote safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For environments_promote, this is the rule to start with:
environments_promote stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every environments_promote call is checked against it from then on.
Questions about environments_promote
Run environments.promote through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
environments_promote accepts 3 parameters: targetKind, targetName, environmentId. Required: targetKind, targetName, environmentId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for environments_promote: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Appaloft. Nothing to install.
environments_promote is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the environments_promote rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for environments_promote. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
environments_promote is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue