RECOMMENDED FOR MULTIPLE CARDS: Adds multiple NEW flashcards to Anki in a single operation. Much more efficient than adding cards one by one. ONLY use this for creating NEW cards, NOT for updating existing ones. Will throw errors for any cards that already exist. For updating existing cards, use ...
AI agents use add_bulk 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, which is a write operation that modifies data reversibly. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool description explicitly states it 'Adds multiple NEW flashcards to Anki in a single operation' and specifies 'ONLY use this for creating NEW cards, NOT for updating existing ones.' This is a create operation that generates new data in the Anki learning…
Documented attack patterns abuse exactly the kind of access add_bulk gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Anki MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_bulk:
{
"version": "1",
"default": "deny",
"tools": {
"add_bulk": {
"limits": [
{
"counter": "add_bulk_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_bulk stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
RECOMMENDED FOR MULTIPLE CARDS: Adds multiple NEW flashcards to Anki in a single operation. Much more efficient than adding cards one by one. ONLY use this for creating NEW cards, NOT for updating existing ones. Will throw errors for any cards that already exist. For updating existing cards, use bulk_update_notes with noteIds instead. Must use HTML formatting for card content. 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 add_bulk: 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.
add_bulk 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 add_bulk 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 add_bulk. 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.
add_bulk is provided by the Anki MCP Server MCP server (nietus/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Anki MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 Anki MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.