Invokes the Card Browser dialog and searches for a given query. Returns an array of identifiers of the cards that were found. Optionally, the reorderCards property can be provided to reorder the cards shown in the Card Browser. This is an array including the order and columnId objects. order can ...
AI agents call gui_browse 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.
gui_browse is a retrieval and query operation that searches existing flashcards and returns results. While it invokes a GUI dialog, this is a presentational action without side effects. The tool neither modifies, deletes, nor executes external operations—it purely queries and retrieves card identifiers from the Anki database. This fits the Read category with low severity due to minimal blast radius from misuse.
From the tool's definition Tool description states it 'searches for a given query' and 'Returns an array of identifiers of the cards that were found.' The reorderCards property only affects display ordering, not data modification.
Attacks that exploit this kind of access
Invokes the Card Browser dialog and searches for a given query. Returns an array of identifiers of the cards that were found. Optionally, the reorderCards property can be provided to reorder the cards shown in the Card Browser. This is an array including the order and columnId objects. order can be either ascending or descending while columnId can be one of several column identifiers (as documented in the Anki source code). The specified column needs to be visible in the Card Browser. 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 gui_browse: 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.
gui_browse 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 gui_browse 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_browse. 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_browse is provided by the Anki MCP Server MCP server (loonskai/anki-mcp-server). 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 →