model_field_remove

A destructive tool on the Anki MCP server.

SERVERAnki SOURCE@arielbk/anki-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-arielbk-anki-mcp/model-field-remove.md

WHAT IT DOES

What model_field_remove does on Anki

AI agents call model_field_remove to permanently remove resources in Anki, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why model_field_remove is rated Critical

Removing a model field in Anki is a destructive operation — it permanently deletes the field definition and all associated data from every note using that model. This cannot be undone. The 'remove' suffix is a strong indicator of irreversible deletion. Confidence is reduced slightly due to the empty description.

From the tool's definition Tool name 'model_field_remove' strongly implies irreversible deletion of a field from an Anki note model/template. The description is empty, so classification is based on name alone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs model_field_remove 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_remove, this is the rule to start with:

model_field_remove Hidden

model_field_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "model_field_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Anki, apply this rule, and every model_field_remove call is checked against it from then on.

FAQ

Questions about model_field_remove

What does the model_field_remove tool do? +

model_field_remove is a destructive tool on the Anki MCP server. It is categorised as a Destructive tool in the Anki MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on model_field_remove? +

Register the Anki MCP server in PolicyLayer and add a rule for model_field_remove: 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.

What risk level is model_field_remove? +

model_field_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit model_field_remove? +

Yes. Add a rate_limit block to the model_field_remove 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.

How do I block model_field_remove completely? +

Set action: deny in the PolicyLayer policy for model_field_remove. 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.

What MCP server provides model_field_remove? +

model_field_remove 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.

KEEP EXPLORING

More on Anki, and thousands of servers like it.

This server

All 98 Anki tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →