AI agents call leave_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.
Leaving a workspace is effectively a destructive action: it removes the current user's membership from the workspace. This cannot typically be undone without an admin re-inviting the user, making it irreversible from the leaving user's perspective. Given the context of a secrets management platform, losing workspace access could have significant blast radius (inability to access secrets, variables, environments).
From the tool's definition 'Leaves a workspace' — leaving a workspace is an irreversible membership action that removes the agent/user from the workspace, potentially losing access permanently with no undo mechanism.
Documented attack patterns abuse exactly the kind of access leave_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 leave_workspace:
{
"version": "1",
"default": "deny",
"hide": [
"leave_workspace"
]
}leave_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.
Leaves 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 leave_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.
leave_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 leave_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 leave_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.
leave_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.