Delete a space from a project. Cannot delete the default space (ID 1).
AI agents call codecks_delete_space to permanently remove resources in Codecks MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a space from a project, which is an irreversible operation that destroys data. Deletion operations are categorized as Destructive per the classification rules. The high severity reflects that deleting a space likely cascades to remove associated cards, decks, and workflows within that space, representing a significant blast radius if invoked incorrectly by an AI agent.
From the tool's definition Delete a space from a project. Cannot delete the default space (ID 1).
Attacks that exploit this kind of access
Delete a space from a project. Cannot delete the default space (ID 1). It is categorised as a Destructive tool in the Codecks MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Codecks MCP Server MCP server in PolicyLayer and add a rule for codecks_delete_space: 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 Codecks MCP Server. Nothing to install.
codecks_delete_space 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 codecks_delete_space 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 codecks_delete_space. 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.
codecks_delete_space is provided by the Codecks MCP Server MCP server (microkorg/codecks-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 →