Suspends the specified cards. Returns true on success.
AI agents use suspend 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.
Suspending cards is a reversible modification of card metadata/state in Anki. While this changes data (card suspension status), it is not destructive (cards are not deleted and can be unsuspended) and does not execute arbitrary code or trigger external side effects. This is a Write-category operation with medium severity because misuse could hide learning materials from the user, but the action is easily reversible.
From the tool's definition The tool 'suspend' modifies card state by suspending specified cards, changing their status from active to suspended. The description states it 'Suspends the specified cards. Returns true on success,' indicating a state modification operation.
Documented attack patterns abuse exactly the kind of access suspend gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Anki, and nothing reaches the server without passing your rules. This is the rule we recommend for suspend:
{
"version": "1",
"default": "deny",
"tools": {
"suspend": {
"limits": [
{
"counter": "suspend_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}suspend 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.
Free to start. No card required.
Suspends the specified cards. Returns true on success. 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 suspend: 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.
suspend 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 suspend 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 suspend. 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.
suspend is provided by the Anki MCP server (ujisati/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Anki, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
40 Anki tools catalogued and risk-classified — across an index of 43,000+ MCP servers.