gui_select_card

A execute tool on the Anki MCP server.

SERVERAnki SOURCE@arielbk/anki-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-arielbk-anki-mcp/gui-select-card.md

WHAT IT DOES

What gui_select_card does on Anki

AI agents invoke gui_select_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.

RISK

Why gui_select_card is rated High

Based on the name pattern 'gui_' consistent with other sibling tools that trigger GUI actions (gui_browse, gui_answer_card, gui_current_card), this tool likely selects/navigates to a card in the Anki GUI. This is an Execute-level action as it triggers an external application UI operation. Confidence is low due to empty description.

From the tool's definition Tool name 'gui_select_card' suggests a GUI interaction (selecting a card in Anki's interface), but the description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gui_select_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_select_card, this is the rule to start with:

gui_select_card Rate-limited

gui_select_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gui_select_card": {
      "limits": [
        {
          "counter": "gui_select_card_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every gui_select_card call is checked against it from then on.

FAQ

Questions about gui_select_card

What does the gui_select_card tool do? +

gui_select_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.

How do I enforce a policy on gui_select_card? +

Register the Anki MCP server in PolicyLayer and add a rule for gui_select_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.

What risk level is gui_select_card? +

gui_select_card is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gui_select_card? +

Yes. Add a rate_limit block to the gui_select_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.

How do I block gui_select_card completely? +

Set action: deny in the PolicyLayer policy for gui_select_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.

What MCP server provides gui_select_card? +

gui_select_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.

KEEP EXPLORING

More on Anki, and thousands of servers like it.

This server

All 98 Anki tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →