Set due date, forget, or relearn one or more cards.
AI agents use reschedule_cards to create or update resources in MCP-AnkiConnect — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-AnkiConnect environment.
The tool modifies card state (due dates, learning status) but does not irreversibly delete data. Rescheduling and relearning are Write operations because they change stored metadata reversibly. Severity is medium because misuse could disrupt a user's study schedule or learning progression, but the effects are correctable and don't involve data destruction, execution of arbitrary code, or financial impact.
From the tool's definition Tool description states it can 'Set due date, forget, or relearn one or more cards' — these are modifications to card scheduling metadata that are reversible through other tool operations (e.g., reschedule_cards can be called again, reviews can be submitted…
Documented attack patterns abuse exactly the kind of access reschedule_cards gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-AnkiConnect, and nothing reaches the server without passing your rules. This is the rule we recommend for reschedule_cards:
{
"version": "1",
"default": "deny",
"tools": {
"reschedule_cards": {
"limits": [
{
"counter": "reschedule_cards_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} reschedule_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.
Free to start. No card required.
Set due date, forget, or relearn one or more cards. It is categorised as a Write tool in the MCP-AnkiConnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-AnkiConnect MCP server in PolicyLayer and add a rule for reschedule_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 MCP-AnkiConnect. Nothing to install.
reschedule_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 reschedule_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 reschedule_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.
reschedule_cards is provided by the MCP-AnkiConnect MCP server (samefarrar/mcp-ankiconnect). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-AnkiConnect, 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.
10 MCP-AnkiConnect tools catalogued and risk-classified — across an index of 43,000+ MCP servers.