Get cards due for review with filtering options
AI agents call getReviewQueue 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 queries and retrieves cards that are due for review from the Anki deck. It performs a read-only operation without creating, modifying, deleting, or executing any side effects. The filtering options are for data retrieval purposes only. No data is altered, and no external operations are triggered, making this a straightforward Read category tool with low risk.
From the tool's definition Tool name 'getReviewQueue' and description 'Get cards due for review with filtering options' indicate a retrieval operation with no modifications or destructive actions.
Attacks that exploit this kind of access
Get cards due for review with filtering options. 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 getReviewQueue: 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.
getReviewQueue 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 getReviewQueue 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 getReviewQueue. 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.
getReviewQueue is provided by the Anki MCP Server MCP server (zlatanpham/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 →