This record as markdown: /tools/io-github-arielbk-anki-mcp/model-field-rename.md
What model_field_rename does on Anki
AI agents use model_field_rename 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 model_field_rename is rated Medium
Renaming a model field is a reversible write operation that modifies Anki's schema but does not delete data or execute arbitrary code. It changes the structure of stored flashcard data, making it Write rather than Read. It is not Destructive because field renames are typically reversible (renaming back is possible), and there is no financial or execution component.
From the tool's definition Tool name 'model_field_rename' indicates renaming a field in an Anki card model. Given the sibling tools like 'add_note', 'add_tags_to_notes', and other write operations, this modifies Anki data structure. The description is empty, reducing certainty.
Attacks that exploit this kind of access
The rule that runs model_field_rename 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 model_field_rename, this is the rule to start with:
model_field_rename 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 model_field_rename call is checked against it from then on.
Questions about model_field_rename
model_field_rename 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 model_field_rename: 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.
model_field_rename 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 model_field_rename 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 model_field_rename. 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.
model_field_rename 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