AI agents use update_note to create or update resources in Anki — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anki environment.
This tool modifies existing notes in Anki (fields and tags) but does not delete or destroy data irreversibly. Updates are reversible through subsequent edits or undo operations, making it a Write operation rather than Destructive. The presence of conflict detection mitigates some risk but doesn't eliminate the potential for unintended data modification if an AI agent misuses field update parameters.
From the tool's definition Tool description explicitly states it 'Update[s] note fields or tags', which are reversible modifications to existing data. The 'optimistic mod-timestamp conflict detection' indicates safeguards against concurrent edits.
Attacks that exploit this kind of access
Update note fields or tags with optimistic mod-timestamp conflict detection. It is categorised as a Write tool in the Anki MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Anki MCP server in PolicyLayer and add a rule for update_note: 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. Nothing to install.
update_note 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 update_note 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 update_note. 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.
update_note is provided by the Anki MCP server (yama662607/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 →