This record as markdown: /tools/io-github-arielbk-anki-mcp/check-cards-due.md
What check_cards_due does on Anki
AI agents call check_cards_due 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 check_cards_due is rated Low
The tool appears to query the state of due/pending cards in Anki without modifying data. This is a typical read operation with minimal risk. While the description is empty (reducing confidence slightly), the name and sibling tools (e.g., answer_cards, add_note for modifications) contextually support classifying this as a retrieval function rather than a write, execute, or destructive action.
From the tool's definition Tool name 'check_cards_due' indicates a query operation that retrieves information about pending flashcards. No description provided, but the naming convention (check_*) and context within an Anki MCP server strongly suggests a read-only status check.
Attacks that exploit this kind of access
The rule that runs check_cards_due 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 check_cards_due, this is the rule to start with:
check_cards_due 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 check_cards_due call is checked against it from then on.
Questions about check_cards_due
check_cards_due is a read tool on the Anki MCP server. 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 check_cards_due: 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.
check_cards_due 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 check_cards_due 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 check_cards_due. 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.
check_cards_due 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