Medium Risk

gui_select_note

gui_select_note

Part of the Anki server.

gui_select_note can modify Anki data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ANKI →

Free to start. No card required.

AI agents use gui_select_note to create or modify resources in Anki. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call gui_select_note repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Anki.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gui_select_note": {
      "limits": [
        {
          "counter": "gui_select_note_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Anki policy for all 25 tools.

Get this rule live on your own Anki server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ANKI →

View all 25 tools →

These attack patterns abuse exactly the kind of access gui_select_note gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so gui_select_note only ever does what you allow.

SECURE ANKI →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the gui_select_note tool do? +

gui_select_note. It is categorised as a Write tool in the Anki MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gui_select_note? +

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

gui_select_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gui_select_note? +

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

Set action: deny in the PolicyLayer policy for gui_select_note. 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_note? +

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

Enforce policy on every Anki tool call.

Deterministic rules across all 25 Anki tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.