deployments_force_redeploy
Run deployments.force-redeploy through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/deployments-force-redeploy.md
What deployments_force_redeploy does on Appaloft
AI agents invoke deployments_force_redeploy 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 |
|---|---|---|---|
serverId | string | — | |
projectId | string | — | |
resourceId | string | Yes | |
destinationId | string | — | |
environmentId | string | — | |
sourceDeploymentId | string | — | |
readinessGeneratedAt | string | — |
Parameters from the server's own tool schema.
Why deployments_force_redeploy is rated High
Force redeployment actively triggers infrastructure operations (restarting/redeploying an application), which is an external execution action. While not directly destructive or financial, it can cause downtime, overwrite running state, or have cascading effects on production systems. The 'force' qualifier indicates it bypasses normal safeguards, raising severity to high.
From the tool's definition 'force-redeploy' — triggers an external deployment operation, rerunning/restarting application deployments
Attacks that exploit this kind of access
The rule that runs deployments_force_redeploy 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_force_redeploy, this is the rule to start with:
deployments_force_redeploy 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 deployments_force_redeploy call is checked against it from then on.
Questions about deployments_force_redeploy
Run deployments.force-redeploy 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.
deployments_force_redeploy accepts 7 parameters: serverId, projectId, resourceId, destinationId, environmentId, sourceDeploymentId, readinessGeneratedAt. Required: resourceId. 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_force_redeploy: 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_force_redeploy 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 deployments_force_redeploy 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_force_redeploy. 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_force_redeploy 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