This record as markdown: /tools/io-github-arielbk-anki-mcp/gui-add-cards.md
What gui_add_cards does on Anki
AI agents use gui_add_cards 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.
Why gui_add_cards is rated Medium
Adding cards to an Anki deck creates new data entries in the flashcard collection. This is reversible (cards can be deleted later) and does not destroy data, so it falls under Write rather than Destructive.
From the tool's definition Tool name 'gui_add_cards' indicates it adds/creates new flashcard entries in the Anki database. The 'gui_' prefix suggests it interacts with the graphical user interface to perform card creation operations.
Attacks that exploit this kind of access
The rule that runs gui_add_cards 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_add_cards, this is the rule to start with:
gui_add_cards 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every gui_add_cards call is checked against it from then on.
Questions about gui_add_cards
gui_add_cards 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.
Register the Anki MCP server in PolicyLayer and add a rule for gui_add_cards: 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.
gui_add_cards is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gui_add_cards 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_add_cards. 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_add_cards 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.
More on Anki, and thousands of servers like it.
This server
Across the catalogue