AI agents use change_deck to create or update resources in MCP-AnkiConnect — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-AnkiConnect environment.
This tool modifies the organizational state of flashcards (deck assignment) but does not delete, destroy, or permanently lose data. The action is reversible — cards can be moved back to their original deck. It is not destructive because it preserves the cards themselves; it is not execute-like because it doesn't run arbitrary code or trigger external operations dependent on complex arguments.
From the tool's definition Tool performs 'Move cards (by card ID) into a different deck' — a reversible modification of card organization/metadata without deletion or financial impact.
Documented attack patterns abuse exactly the kind of access change_deck gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-AnkiConnect, and nothing reaches the server without passing your rules. This is the rule we recommend for change_deck:
{
"version": "1",
"default": "deny",
"tools": {
"change_deck": {
"limits": [
{
"counter": "change_deck_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}change_deck 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.
Move cards (by card ID) into a different deck. It is categorised as a Write tool in the MCP-AnkiConnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-AnkiConnect MCP server in PolicyLayer and add a rule for change_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 MCP-AnkiConnect. Nothing to install.
change_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 change_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 change_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.
change_deck is provided by the MCP-AnkiConnect MCP server (samefarrar/mcp-ankiconnect). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-AnkiConnect, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP-AnkiConnect tools catalogued and risk-classified — across an index of 43,000+ MCP servers.