Submit an arbitrary request through Anki connect
AI agents invoke anki-request to trigger actions in Anki Connect MCP Server. 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.
Because this tool allows arbitrary RPC requests to AnkiConnect, it spans multiple risk categories. Per the rules, the most severe applicable category must be chosen. An arbitrary request could trigger destructive actions (deleting decks/notes), write actions, or execute-style operations.
From the tool's definition 'Submit an arbitrary request through Anki connect' — the word 'arbitrary' indicates this tool can invoke any AnkiConnect API action, which may include destructive operations (delete deck, remove notes), write operations, or other side effects depending on the…
Attacks that exploit this kind of access
Submit an arbitrary request through Anki connect. It is categorised as a Execute tool in the Anki Connect MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Anki Connect MCP Server MCP server in PolicyLayer and add a rule for anki-request: 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 Connect MCP Server. Nothing to install.
anki-request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the anki-request 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 anki-request. 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.
anki-request is provided by the Anki Connect MCP Server MCP server (sergey-mamulchenko/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →