Gets the complete list of model names for the current user.
AI agents call model_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 retrieves metadata (model names) from the Anki application without creating, modifying, deleting, or executing any operations. It is a straightforward query operation with minimal blast radius if misused—an AI agent could at worst enumerate the available models, which poses no security risk.
From the tool's definition Tool name 'model_names' and description 'Gets the complete list of model names' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Gets the complete list of model 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 model_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.
model_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 model_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 model_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.
model_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.
model_names is one line of Anki MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →