更改卡片的笔记类型(模板)
AI agents use anki_change_note_type to create or update resources in TalkToAnki — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TalkToAnki environment.
Changing a note type modifies existing data (the note's template/type field) but is reversible—the original note data is not destroyed, and the operation can be undone or reverted. This fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool name 'anki_change_note_type' and description indicate modification of existing note templates/types. This is a reversible change operation that alters the structure of flashcard data without deleting it.
Attacks that exploit this kind of access
更改卡片的笔记类型(模板). It is categorised as a Write tool in the TalkToAnki MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TalkToAnki MCP server in PolicyLayer and add a rule for anki_change_note_type: 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 TalkToAnki. Nothing to install.
anki_change_note_type 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 anki_change_note_type 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_change_note_type. 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_change_note_type is provided by the TalkToAnki MCP server (muxuuu/talktoanki). 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 →