Gets the configuration group object for the given deck name. Returns the deck configuration object.
AI agents call getDeckConfig to retrieve information from Anki without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns deck configuration data without creating, modifying, deleting, or executing any operations. It is a simple read operation querying Anki deck settings.
From the tool's definition Tool name 'getDeckConfig' and description 'Gets the configuration group object for the given deck name. Returns the deck configuration object.' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access getDeckConfig 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 getDeckConfig:
{
"version": "1",
"default": "deny",
"tools": {
"getDeckConfig": {}
}
}getDeckConfig is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets the configuration group object for the given deck name. Returns the deck configuration object. It is categorised as a Read tool in the Anki MCP Server, which means it retrieves data without modifying state.
Register the Anki MCP server in PolicyLayer and add a rule for getDeckConfig: 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.
getDeckConfig is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getDeckConfig 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 getDeckConfig. 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.
getDeckConfig 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.