Permanently delete cards (requires confirmation)
AI agents call delete_cards to permanently remove resources in Anki MCP Data Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes flashcard data from the user's Anki collection. While the confirmation requirement provides a minor safeguard, an AI agent could still be manipulated into confirming deletion of significant study materials. The blast radius is high because bulk card deletion could destroy weeks or months of learning progress.
From the tool's definition Tool name is "delete_cards" and description states "Permanently delete cards (requires confirmation)" — the word "Permanently" combined with "delete" indicates irreversible destruction of data.
Attacks that exploit this kind of access
Permanently delete cards (requires confirmation). It is categorised as a Destructive tool in the Anki MCP Data Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Anki MCP Data Bridge MCP server in PolicyLayer and add a rule for delete_cards: 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 MCP Data Bridge. Nothing to install.
delete_cards 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_cards 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_cards. 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_cards is provided by the Anki MCP Data Bridge MCP server (stefanspycher/anki-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 →