This record as markdown: /tools/io-github-arielbk-anki-mcp/gui-answer-card.md
What gui_answer_card does on Anki
AI agents invoke gui_answer_card to trigger actions in Anki. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why gui_answer_card is rated High
Based on the name, this tool likely interacts with the Anki GUI to submit an answer for the current card (e.g., Again/Hard/Good/Easy), which constitutes an external operation/browser-like GUI action. This would modify review state. However, the empty description lowers confidence. Given sibling tools like gui_current_card and gui_deck_review, this fits the Execute pattern of triggering external GUI operations.
From the tool's definition Tool name 'gui_answer_card' suggests triggering a GUI action in Anki to answer/rate a flashcard. Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs gui_answer_card 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 gui_answer_card, this is the rule to start with:
gui_answer_card stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 gui_answer_card call is checked against it from then on.
Questions about gui_answer_card
gui_answer_card is a execute tool on the Anki MCP server. It is categorised as a Execute tool in the Anki MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Anki MCP server in PolicyLayer and add a rule for gui_answer_card: 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.
gui_answer_card is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gui_answer_card 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 gui_answer_card. 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.
gui_answer_card 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