Get the complete list of deck names for the current user.
AI agents call deck_names to retrieve information from Anki MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves data (the list of deck names) without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal risk if misused by an AI agent, as it merely exposes information already available to the user.
From the tool's definition Tool name is 'deck_names' and description states 'Get the complete list of deck names for the current user.' The verb 'Get' and the read-only nature of retrieving a list of existing deck names with no modifications indicate a retrieval operation.
Attacks that exploit this kind of access
Get the complete list of deck names for the current user. It is categorised as a Read tool in the Anki MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Anki MCP Server MCP server in PolicyLayer and add a rule for deck_names: 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 MCP Server. Nothing to install.
deck_names 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 deck_names 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 deck_names. 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.
deck_names is provided by the Anki MCP Server MCP server (loonskai/anki-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →