AI agents use create_deck to create or update resources in Anki MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anki MCP Server environment.
Creating a deck is a write operation that modifies the user's Anki collection by adding a new container for flashcards. This is reversible (decks can be deleted), does not execute arbitrary code, and does not involve financial transactions or irreversible data destruction. The blast radius of misuse is limited to the creation of unwanted empty or populated decks in the user's study collection.
From the tool's definition Tool description states 'Create a new Anki deck' — this is a create operation that adds new data to the Anki system in a reversible manner (decks can be deleted).
Documented attack patterns abuse exactly the kind of access create_deck gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Anki MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_deck:
{
"version": "1",
"default": "deny",
"tools": {
"create_deck": {
"limits": [
{
"counter": "create_deck_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Create a new Anki deck. It is categorised as a Write tool in the Anki MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Anki MCP Server MCP server in PolicyLayer and add a rule for create_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 Server. Nothing to install.
create_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 create_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 create_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.
create_deck is provided by the Anki MCP Server MCP server (nietus/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Anki MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 Anki MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.