Delete a deck (disabled by default, requires MOCHI_ALLOW_DECK_DELETE=true)
AI agents call delete_deck to permanently remove resources in Mochi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a deck irreversibly removes an entire collection of flashcards and cannot be undone. This is a Destructive action, not merely Write, because it involves permanent data loss. The high severity reflects that an errant agent call could eliminate all study materials in a deck.
From the tool's definition Tool name is 'delete_deck' with description stating it 'Delete[s] a deck'; explicitly permanent operation with safety feature (disabled by default, requires environment variable MOCHI_ALLOW_DECK_DELETE=true) confirming destructive intent.
Attacks that exploit this kind of access
Delete a deck (disabled by default, requires MOCHI_ALLOW_DECK_DELETE=true). It is categorised as a Destructive tool in the Mochi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mochi MCP Server MCP server in PolicyLayer and add a rule for delete_deck: 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 Mochi MCP Server. Nothing to install.
delete_deck 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_deck 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_deck. 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_deck is provided by the Mochi MCP Server MCP server (nz99/mochi-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 →