This record as markdown: /tools/io-github-arielbk-anki-mcp/remove-deck-config.md
What remove_deck_config does on Anki
AI agents call remove_deck_config to permanently remove resources in Anki, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_deck_config is rated Critical
Removing deck configuration is a destructive operation that cannot be easily undone without restoring from backup. While it doesn't delete the deck itself, it eliminates configuration settings that may affect how the deck functions (study settings, new card limits, etc.).
From the tool's definition Tool name 'remove_deck_config' indicates deletion/removal of deck configuration. The verb 'remove' combined with 'deck_config' (configuration) suggests irreversible deletion of settings.
Attacks that exploit this kind of access
The rule that runs remove_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 remove_deck_config, this is the rule to start with:
remove_deck_config is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every remove_deck_config call is checked against it from then on.
Questions about remove_deck_config
remove_deck_config is a destructive tool on the Anki MCP server. It is categorised as a Destructive tool in the Anki MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Anki MCP server in PolicyLayer and add a rule for remove_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.
remove_deck_config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.
Across the catalogue