RECOMMENDED FOR MULTIPLE CARDS: Update specific fields for multiple EXISTING Anki notes in a single operation. Much more efficient than updating cards one by one. Use this ONLY when you have noteIds for cards that already exist. For creating new cards in bulk, use add_bulk instead. Complete all u...
AI agents use bulk_update_notes 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 or modifies data reversibly—it updates fields in existing Anki notes without deleting them or executing arbitrary code. The blast radius is medium because bulk operations on multiple notes could affect many study records if parameters are incorrect, but changes remain reversible (notes can be re-edited). It does not execute external commands, delete irreversibly, or handle financial transactions.
From the tool's definition Tool description states it 'Update[s] specific fields for multiple EXISTING Anki notes in a single operation' and emphasizes this modifies existing data rather than creating or deleting it.
Documented attack patterns abuse exactly the kind of access bulk_update_notes 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 bulk_update_notes:
{
"version": "1",
"default": "deny",
"tools": {
"bulk_update_notes": {
"limits": [
{
"counter": "bulk_update_notes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bulk_update_notes 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: Update specific fields for multiple EXISTING Anki notes in a single operation. Much more efficient than updating cards one by one. Use this ONLY when you have noteIds for cards that already exist. For creating new cards in bulk, use add_bulk instead. Complete all updates in a single operation whenever possible. 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 bulk_update_notes: 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.
bulk_update_notes 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 bulk_update_notes 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 bulk_update_notes. 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.
bulk_update_notes 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.