This record as markdown: /tools/io-github-arielbk-anki-mcp/gui-exit-anki.md
What gui_exit_anki does on Anki
AI agents call gui_exit_anki to permanently remove resources in Anki, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why gui_exit_anki is rated Critical
Exiting an application can cause loss of unsaved data and interrupt ongoing sessions, which is effectively irreversible in terms of lost work. The empty description lowers confidence, but the name strongly implies closing the Anki GUI. Severity is high because it could disrupt active study sessions and cause data loss.
From the tool's definition Tool name 'gui_exit_anki' suggests it closes/exits the Anki application; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs gui_exit_anki 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_exit_anki, this is the rule to start with:
gui_exit_anki is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every gui_exit_anki call is checked against it from then on.
Questions about gui_exit_anki
gui_exit_anki is a destructive tool on the Anki MCP server. It is categorised as a Destructive tool in the Anki MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Anki MCP server in PolicyLayer and add a rule for gui_exit_anki: 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_exit_anki is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the gui_exit_anki 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_exit_anki. 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_exit_anki 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.
Across the catalogue