get_analytics
Read study analytics and review history for decks, the collection, or specific cards. Use this when the agent needs reporting or diagnostics, not when it needs to mutate Anki data. This tool is read-only but some scopes can return large payloads, so prefer the narrowest scope and explicit card ID...
This record as markdown: /tools/io-github-arielbk-anki-mcp/get-analytics.md
What get_analytics does on Anki
AI agents call get_analytics to retrieve information from Anki without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_analytics is rated Low
This tool retrieves and queries analytics data without modifying, deleting, or executing operations. It has no side effects on the Anki database or system state. The read-only designation and analytics retrieval purpose clearly place it in the Read category. Severity is low because the blast radius of misuse is limited to information disclosure of the user's study history, which has no irreversible consequences.
From the tool's definition Tool description explicitly states "Read study analytics and review history" and "This tool is read-only". The name "get_analytics" follows read operation naming conventions.
Attacks that exploit this kind of access
The rule that runs get_analytics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Anki, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_analytics, this is the rule to start with:
get_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every get_analytics call is checked against it from then on.
Questions about get_analytics
Read study analytics and review history for decks, the collection, or specific cards. Use this when the agent needs reporting or diagnostics, not when it needs to mutate Anki data. This tool is read-only but some scopes can return large payloads, so prefer the narrowest scope and explicit card IDs or timestamps when available. Choose. 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_analytics: 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_analytics 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_analytics 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_analytics. 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_analytics is provided by the Anki MCP server (@arielbk/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Anki, and thousands of servers like it.
This server
Across the catalogue