This record as markdown: /tools/io-github-arielbk-anki-mcp/delete-decks.md
What delete_decks does on Anki
AI agents call delete_decks to permanently remove resources in Anki, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_decks is rated Critical
Deleting decks removes study materials and associated cards/notes permanently. This is a destructive operation (not merely Write) because it cannot be reversed and results in data loss. High severity because a misused agent could destroy a user's study collections. Confidence is high despite empty description because the tool name is explicit and unambiguous.
From the tool's definition Tool name 'delete_decks' indicates irreversible deletion of Anki deck data. No description provided, but the name unambiguously describes a destructive operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_decks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Anki, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_decks, this is the rule to start with:
delete_decks is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every delete_decks call is checked against it from then on.
Questions about delete_decks
delete_decks is a destructive tool on the Anki MCP server. It is categorised as a Destructive tool in the Anki MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Anki MCP server in PolicyLayer and add a rule for delete_decks: 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 Anki. Nothing to install.
delete_decks 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_decks 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_decks. 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_decks is provided by the Anki MCP server (@arielbk/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Anki, and thousands of servers like it.
Across the catalogue