Move cards between decks
AI agents use move_cards_to_deck 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 (deck assignment) without deleting or destroying data. The operation is reversible (cards can be moved back), placing it in the Write category rather than Destructive. Severity is medium because moving cards between decks could disrupt spaced repetition scheduling or organization if misapplied at scale, but the effects are recoverable.
From the tool's definition Tool description states 'Move cards between decks' — this modifies the organizational structure and location of cards within the Anki database, which is a reversible write operation.
Attacks that exploit this kind of access
Move cards between decks. 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 move_cards_to_deck: 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.
move_cards_to_deck 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 move_cards_to_deck 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 move_cards_to_deck. 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.
move_cards_to_deck 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 →