AI agents call get_runtime_status 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 performs a status check by probing AnkiConnect reachability and extension availability. It retrieves information about runtime conditions without modifying, executing operations on, or deleting any data. This is a pure Read operation with minimal security risk.
From the tool's definition Tool name 'get_runtime_status' and description 'Report whether AnkiConnect is reachable and whether preview can use the optional extension path' indicate querying/status checking with no side effects.
Attacks that exploit this kind of access
Report whether AnkiConnect is reachable and whether preview can use the optional extension path. 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 get_runtime_status: 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.
get_runtime_status 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 get_runtime_status 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 get_runtime_status. 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.
get_runtime_status is provided by the Anki MCP server (yama662607/anki-mcp). 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 →