AI agents use rename_note_type_field to create or update resources in Anki MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anki MCP Server environment.
This tool modifies an existing note type field by renaming it, which is a reversible write operation. It changes configuration metadata but does not delete data, execute arbitrary code, or cause financial impact. The severity is medium because renaming fields could affect dependent cards and queries if done incorrectly, but the operation is reversible through another rename operation.
From the tool's definition Tool name 'rename_note_type_field' and description 'Renames a field in a note type' indicate modification of existing schema/metadata structures within Anki's note system.
Documented attack patterns abuse exactly the kind of access rename_note_type_field gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Anki MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_note_type_field:
{
"version": "1",
"default": "deny",
"tools": {
"rename_note_type_field": {
"limits": [
{
"counter": "rename_note_type_field_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_note_type_field 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.
Renames a field in a note type. It is categorised as a Write tool in the Anki MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Anki MCP Server MCP server in PolicyLayer and add a rule for rename_note_type_field: 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 MCP Server. Nothing to install.
rename_note_type_field 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 rename_note_type_field 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 rename_note_type_field. 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.
rename_note_type_field is provided by the Anki MCP Server MCP server (nietus/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Anki MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 Anki MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.