This record as markdown: /tools/io-github-arielbk-anki-mcp/clone-deck-config.md
What clone_deck_config does on Anki
AI agents use clone_deck_config to create or update resources in Anki, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anki environment.
Why clone_deck_config is rated Medium
Cloning a deck configuration is a reversible write operation—it creates new configuration data in Anki. It does not execute arbitrary code, destroy data, or move money. The empty description reduces confidence somewhat, but the tool name and server context strongly indicate a Write classification.
From the tool's definition Tool name 'clone_deck_config' indicates copying/duplicating deck configuration settings. The description is empty, but context from sibling tools (add_note, add_tags_to_notes, change_deck) suggests this server performs reversible modifications to Anki data…
Attacks that exploit this kind of access
The rule that runs clone_deck_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Anki, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clone_deck_config, this is the rule to start with:
clone_deck_config 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every clone_deck_config call is checked against it from then on.
Questions about clone_deck_config
clone_deck_config is a write tool on the Anki MCP server. It is categorised as a Write tool in the Anki MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Anki MCP server in PolicyLayer and add a rule for clone_deck_config: 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. Nothing to install.
clone_deck_config 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 clone_deck_config 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 clone_deck_config. 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.
clone_deck_config is provided by the Anki MCP server (@arielbk/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Anki, and thousands of servers like it.
This server
Across the catalogue