批量更新卡片标签
AI agents use anki_batch_update_tags to create or update resources in TalkToAnki — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TalkToAnki environment.
This tool modifies card tags in bulk, which is reversible (tags can be changed again or removed). It does not delete data irreversibly, execute arbitrary code, or trigger financial transactions. It fits the Write category: creates or modifies data reversibly. Severity is medium because bulk modifications could affect study workflows if misapplied to many cards, but the effect is reversible.
From the tool's definition Tool name 'anki_batch_update_tags' with description indicating batch tag updates on cards. The 'batch' and 'update' operations clearly modify existing flashcard metadata (tags) in bulk.
Attacks that exploit this kind of access
批量更新卡片标签. It is categorised as a Write tool in the TalkToAnki MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TalkToAnki MCP server in PolicyLayer and add a rule for anki_batch_update_tags: 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 TalkToAnki. Nothing to install.
anki_batch_update_tags 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 anki_batch_update_tags 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 anki_batch_update_tags. 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.
anki_batch_update_tags is provided by the TalkToAnki MCP server (muxuuu/talktoanki). 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 →