Destroy a workspace and all its processes.
AI agents call destroy_workspace to permanently remove resources in Persistent Shell MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes workspaces and terminates all running processes within them. While not data deletion in the traditional sense, workspace destruction is an irreversible operation with significant blast radius—an AI agent misusing this could eliminate entire development/execution environments and their state. This exceeds Execute severity because the effects are permanent and unrecoverable.
From the tool's definition The tool is explicitly named 'destroy_workspace' and described as 'Destroy a workspace and all its processes.' The verb 'destroy' combined with the irreversible termination of entire workspaces and their associated processes indicates destructive action that…
Attacks that exploit this kind of access
Destroy a workspace and all its processes. It is categorised as a Destructive tool in the Persistent Shell MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Persistent Shell MCP server in PolicyLayer and add a rule for destroy_workspace: 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 Persistent Shell MCP. Nothing to install.
destroy_workspace 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 destroy_workspace 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 destroy_workspace. 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.
destroy_workspace is provided by the Persistent Shell MCP server (tntisdial/persistent-shell-mcp). 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 →