Saves the given configuration group. Returns true on success, false otherwise.
AI agents use saveDeckConfig 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.
This tool modifies Anki deck configuration settings, which is a reversible operation (configurations can be updated or reverted). It does not delete data (Destructive), execute arbitrary code (Execute), or create financial obligations (Financial).
From the tool's definition Tool name 'saveDeckConfig' and description 'Saves the given configuration group' indicate creation or modification of deck configuration settings.
Documented attack patterns abuse exactly the kind of access saveDeckConfig gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Anki, and nothing reaches the server without passing your rules. This is the rule we recommend for saveDeckConfig:
{
"version": "1",
"default": "deny",
"tools": {
"saveDeckConfig": {
"limits": [
{
"counter": "savedeckconfig_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}saveDeckConfig 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.
Saves the given configuration group. Returns true on success, false otherwise. 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 saveDeckConfig: 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.
saveDeckConfig 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 saveDeckConfig 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 saveDeckConfig. 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.
saveDeckConfig is provided by the Anki MCP server (ujisati/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Anki, 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.
40 Anki tools catalogued and risk-classified — across an index of 43,000+ MCP servers.