Gets the complete list of deck names for the current user. Returns a list of deck names.
AI agents call deckNames 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 existing deck names from the Anki collection without creating, modifying, deleting, or executing any operations. It is a simple query operation with no side effects, fitting the Read category. Severity is low because access to deck names poses minimal security risk—it is metadata about the user's study structure with no sensitive personal data, financial implications, or destructive capabilities.
From the tool's definition Tool name is 'deckNames' and description states it 'Gets the complete list of deck names' and 'Returns a list of deck names.' The verb 'Gets' and the read-only nature of returning a list indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access deckNames 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 deckNames:
{
"version": "1",
"default": "deny",
"tools": {
"deckNames": {}
}
}deckNames 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 complete list of deck names for the current user. Returns a list of deck names. 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 deckNames: 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.
deckNames 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 deckNames 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 deckNames. 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.
deckNames 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.