Add tags to multiple cards without replacing existing tags
AI agents use add_tags_to_cards to create or update resources in Anki MCP Data Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anki MCP Data Bridge environment.
This tool modifies card metadata (tags) in a reversible manner. It creates new associations rather than destroying data or executing arbitrary code. While it affects multiple cards, the blast radius is limited to tag metadata with no impact on card content or financial operations. This is a straightforward Write operation on flashcard metadata.
From the tool's definition Tool name 'add_tags_to_cards' and description 'Add tags to multiple cards without replacing existing tags' indicates modification of existing data.
Attacks that exploit this kind of access
Add tags to multiple cards without replacing existing tags. It is categorised as a Write tool in the Anki MCP Data Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Anki MCP Data Bridge MCP server in PolicyLayer and add a rule for add_tags_to_cards: 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 Data Bridge. Nothing to install.
add_tags_to_cards 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_tags_to_cards 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_tags_to_cards. 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_tags_to_cards is provided by the Anki MCP Data Bridge MCP server (stefanspycher/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 →