Add multiple cards to a deck in batch
AI agents use addCardsBatch 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 new flashcard entries in an Anki deck, which is reversible (cards can be deleted). It does not execute code, destroy data irreversibly, or move money. Batch creation of cards is a write operation with moderate blast radius—incorrect bulk additions could clutter a deck but remain recoverable. Confidence is high as the name and description clearly indicate card creation/addition.
From the tool's definition Tool name 'addCardsBatch' and description 'Add multiple cards to a deck in batch' indicate creation of multiple data records in the Anki flashcard system.
Attacks that exploit this kind of access
Add multiple cards to a deck in batch. 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 addCardsBatch: 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.
addCardsBatch 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 addCardsBatch 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 addCardsBatch. 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.
addCardsBatch 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 →