Low Risk

get_deck_names

Get a list of all Anki deck names.

How to control get_deck_names ↓

AI agents call get_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.

Low Risk

This tool retrieves and lists existing data (deck names) without side effects. It performs a query-like operation typical of Read category tools. No data is created, modified, deleted, or executed. Severity is low because listing deck names poses minimal security risk even if accessed without authorization, as it reveals only organizational metadata.

From the tool's definition Tool name is 'get_deck_names' and description states 'Get a list of all Anki deck names' — a straightforward retrieval operation with no modification, deletion, or execution.

Documented attack patterns abuse exactly the kind of access get_deck_names gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Anki MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_deck_names:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_deck_names": {}
  }
}

get_deck_names is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Anki MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_deck_names tool do? +

Get a list of all Anki deck names. It is categorised as a Read tool in the Anki MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_deck_names? +

Register the Anki MCP Server MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_deck_names? +

get_deck_names is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_deck_names? +

Yes. Add a rate_limit block to the get_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.

How do I block get_deck_names completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_deck_names? +

get_deck_names is provided by the Anki MCP Server MCP server (nietus/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Anki MCP Server tool call.

Deterministic rules across all 22 Anki MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

22 Anki MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.