Delete a workspace and all its content (cannot delete default workspace)
AI agents call delete_workspace to permanently remove resources in Sidvy MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes an entire workspace and all associated data. This is a destructive action that cannot be undone, making it fall squarely into the Destructive category. The severity is high because a compromised AI agent could wipe out significant user data and work. Confidence is high due to explicit language in the description.
From the tool's definition Tool name is 'delete_workspace' and description states 'Delete a workspace and all its content' — explicit deletion operation.
Attacks that exploit this kind of access
Delete a workspace and all its content (cannot delete default workspace). It is categorised as a Destructive tool in the Sidvy MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sidvy MCP Server 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 Sidvy MCP Server. 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 Sidvy MCP Server MCP server (martinhjartmyr/sidvy-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 →