deployments_plan
Read deployments.plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/deployments-plan.md
What deployments_plan does on Appaloft
AI agents call deployments_plan to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
serverId | string | Yes | |
projectId | string | Yes | |
resourceId | string | Yes | |
destinationId | string | — | |
environmentId | string | Yes | |
includeAccessPlan | object | — | |
includeCommandSpecs | object | — |
Parameters from the server's own tool schema.
Why deployments_plan is rated Low
The description explicitly states this tool 'reads' deployment plan data. It retrieves/queries information with no indicated side effects, consistent with a Read category. Severity is low as it only exposes deployment configuration data.
From the tool's definition "Read deployments.plan through the Appaloft application operation catalog"
Attacks that exploit this kind of access
The rule that runs deployments_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 deployments_plan, this is the rule to start with:
deployments_plan is read-only, so it stays allowed. 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 deployments_plan call is checked against it from then on.
Questions about deployments_plan
Read deployments.plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
deployments_plan accepts 7 parameters: serverId, projectId, resourceId, destinationId, environmentId, includeAccessPlan, includeCommandSpecs. Required: serverId, projectId, resourceId, 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 deployments_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.
deployments_plan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the deployments_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 deployments_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.
deployments_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.
This server
Across the catalogue