gui_current_card

A read tool on the Anki MCP server.

SERVERAnki SOURCE@arielbk/anki-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What gui_current_card does on Anki

AI agents call gui_current_card to retrieve information from Anki without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why gui_current_card is rated Low

Based on the tool name, it likely retrieves the currently displayed card in the Anki GUI, which is a read operation. The 'gui_' prefix and sibling tools like 'gui_browse', 'gui_deck_browser' suggest this is a read/query operation. Confidence is lowered due to empty description.

From the tool's definition Tool name is 'gui_current_card'; description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gui_current_card Allowed

gui_current_card is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gui_current_card": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about gui_current_card

What does the gui_current_card tool do? +

gui_current_card is a read tool on the Anki MCP server. It is categorised as a Read tool in the Anki MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gui_current_card? +

Register the Anki MCP server in PolicyLayer and add a rule for gui_current_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_current_card? +

gui_current_card is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gui_current_card? +

Yes. Add a rate_limit block to the gui_current_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_current_card completely? +

Set action: deny in the PolicyLayer policy for gui_current_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_current_card? +

gui_current_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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →