deployments_archive
Run deployments.archive through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/deployments-archive.md
What deployments_archive does on Appaloft
AI agents call deployments_archive to permanently remove resources in Appaloft, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | string | Yes | |
resourceId | string | — | |
deploymentId | string | Yes |
Parameters from the server's own tool schema.
Why deployments_archive is rated Critical
Archiving a deployment is generally a destructive or at minimum irreversible action — it removes the deployment from active service. The sibling tool naming conventions (prune, delete, revoke) reinforce that 'archive' here likely means a one-way state change, warranting a Destructive classification with high severity due to the blast radius of taking down a deployment.
From the tool's definition 'deployments_archive' and 'Run deployments.archive' — archiving a deployment typically renders it inactive or removes it from active use in an irreversible manner; sibling tools like 'audit_events_archives_prune' and 'account_delete' suggest destructive…
Attacks that exploit this kind of access
The rule that runs deployments_archive 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_archive, this is the rule to start with:
deployments_archive is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every deployments_archive call is checked against it from then on.
Questions about deployments_archive
Run deployments.archive through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deployments_archive accepts 3 parameters: confirm, resourceId, deploymentId. Required: confirm, deploymentId. 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_archive: 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_archive is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deployments_archive 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_archive. 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_archive 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