Add a cloze deletion card to a deck
AI agents use addClozeCard to create or update resources in Anki MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anki MCP Server environment.
This tool creates a new cloze deletion card in an Anki deck. Creating data is a Write operation. Severity is low because: (1) the action is reversible—cards can be deleted; (2) the blast radius is limited to flashcard study material with no external consequences; (3) misuse would only affect the user's own Anki learning system. The tool does not execute code, modify financial systems, or permanently destroy data.
From the tool's definition Tool name 'addClozeCard' and description 'Add a cloze deletion card to a deck' indicate creation of new flashcard data.
Attacks that exploit this kind of access
Add a cloze deletion card to a deck. It is categorised as a Write tool in the Anki MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Anki MCP Server MCP server in PolicyLayer and add a rule for addClozeCard: 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 Server. Nothing to install.
addClozeCard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the addClozeCard 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 addClozeCard. 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.
addClozeCard is provided by the Anki MCP Server MCP server (zlatanpham/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 →