AI agents call delete_workspace to permanently remove resources in Keyshade — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a workspace is a destructive action that cannot be undone. It permanently removes a container resource and all nested data, representing the highest severity risk category. The operation has organization-wide blast radius if invoked by a compromised or misdirected AI agent, potentially eliminating critical infrastructure and secret management access across multiple projects and teams.
From the tool's definition Tool name is 'delete_workspace' and description states 'Deletes a workspace'. This is an irreversible deletion operation that removes an entire workspace and likely all associated data (projects, secrets, environments, roles) stored within it.
Documented attack patterns abuse exactly the kind of access delete_workspace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Keyshade, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_workspace:
{
"version": "1",
"default": "deny",
"hide": [
"delete_workspace"
]
}delete_workspace disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes a workspace. It is categorised as a Destructive tool in the Keyshade MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Keyshade MCP server in PolicyLayer and add a rule for delete_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 Keyshade. Nothing to install.
delete_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 delete_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 delete_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.
delete_workspace is provided by the Keyshade MCP server (keyshade-xyz/keyshade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Keyshade, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
44 Keyshade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.