gui_import_file

A write tool on the Anki MCP server.

SERVERAnki SOURCE@arielbk/anki-mcp

Medium RISK CLASS

Category Write

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-import-file.md

WHAT IT DOES

What gui_import_file does on Anki

AI agents use gui_import_file to create or update resources in Anki, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anki environment.

RISK

Why gui_import_file is rated Medium

Import tools reversibly add or update data in a system (Write category). Since the description is empty, confidence is moderate. Severity is medium because importing malicious or incorrect data could corrupt an Anki collection, but the damage is potentially reversible through backups or undo operations, unlike destructive actions.

From the tool's definition Tool name 'gui_import_file' suggests importing/loading data into Anki; sibling tools like 'gui_add_cards' and 'anki_operations' indicate this server manipulates Anki collections. Import operations typically create or modify card data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gui_import_file Rate-limited

gui_import_file stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_import_file": {
      "limits": [
        {
          "counter": "gui_import_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_import_file call is checked against it from then on.

FAQ

Questions about gui_import_file

What does the gui_import_file tool do? +

gui_import_file is a write tool on the Anki MCP server. 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_import_file? +

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

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

Can I rate-limit gui_import_file? +

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

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

gui_import_file 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

write_file on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →