Permanently delete one inactive deployment. Explain the impact first and require exact user confirmation.
AI agents call staticx_delete_deployment to permanently remove resources in StaticX MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes deployment data with no undo capability. Although the tool requires user confirmation and targets only inactive deployments (mitigating factors), the permanent deletion of infrastructure/deployment records constitutes a destructive action.
From the tool's definition Tool name explicitly states 'delete_deployment' and description confirms 'Permanently delete one inactive deployment.' The use of 'Permanently' and 'delete' indicates irreversible data loss.
Attacks that exploit this kind of access
Permanently delete one inactive deployment. Explain the impact first and require exact user confirmation. It is categorised as a Destructive tool in the StaticX MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the StaticX MCP Server MCP server in PolicyLayer and add a rule for staticx_delete_deployment: 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 StaticX MCP Server. Nothing to install.
staticx_delete_deployment 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 staticx_delete_deployment 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 staticx_delete_deployment. 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.
staticx_delete_deployment is provided by the StaticX MCP Server MCP server (madprodworks-coder/staticx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →