sandboxes_promotions_plan
Run sandboxes.promotions.plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandboxes-promotions-plan.md
What sandboxes_promotions_plan does on Appaloft
AI agents invoke sandboxes_promotions_plan 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 |
|---|---|---|---|
target | object | Yes | |
sandboxId | string | Yes | |
artifactId | string | Yes | |
candidatePreviewId | string | Yes | |
expectedArtifactDigest | string | Yes |
Parameters from the server's own tool schema.
Why sandboxes_promotions_plan is rated High
The tool 'runs' an operation from an application catalog, indicating execution of an action rather than a simple read or write. 'Promotions plan' in a sandbox context likely triggers a planning or promotion pipeline that could have significant side effects. The description is vague, so confidence is moderate, but 'Run' clearly places it in the Execute category.
From the tool's definition 'Run sandboxes.promotions.plan through the Appaloft application operation catalog'
Attacks that exploit this kind of access
The rule that runs sandboxes_promotions_plan 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 sandboxes_promotions_plan, this is the rule to start with:
sandboxes_promotions_plan 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 sandboxes_promotions_plan call is checked against it from then on.
Questions about sandboxes_promotions_plan
Run sandboxes.promotions.plan 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.
sandboxes_promotions_plan accepts 5 parameters: target, sandboxId, artifactId, candidatePreviewId, expectedArtifactDigest. Required: target, sandboxId, artifactId, candidatePreviewId, expectedArtifactDigest. 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 sandboxes_promotions_plan: 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.
sandboxes_promotions_plan 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 sandboxes_promotions_plan 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 sandboxes_promotions_plan. 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.
sandboxes_promotions_plan 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