// MCP TOOL REFERENCE

delete_annotation

ServerLocal Rag
CategoryDestructive

WHAT IT DOES

What delete_annotation does on Local Rag

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

THE RISK

Critical Risk

Why delete_annotation needs a policy

This tool permanently deletes annotations from the codebase metadata. While the blast radius is moderate—annotations are metadata, not code or production systems—the action is irreversible. An agent instructed to clean up annotations could indiscriminately delete important context (bug notes, constraints, documentation). This fits the Destructive category because deletion cannot be undone without recovery mechanisms.

From the tool's definition Tool name 'delete_annotation' and description 'Remove an annotation' indicate irreversible deletion of data (annotations stored in the system).

Documented attack patterns abuse exactly the kind of access delete_annotation gives an agent:

POLICY

How to control delete_annotation

PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_annotation:

policy.json

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

delete_annotation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Local Rag — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Local Rag tools

Destructive remove_file Remove a specific file from the RAG index. Execute wiki Run the wiki rebuild workflow. The Write index_files Index files in a directory for semantic search. Without patterns, indexes the project from Write annotate Attach a persistent note to a file or symbol that surfaces inline in future read_relevant Write create_checkpoint Save a checkpoint so future sessions know what was done and why. REQUIRED: call this as yo Read affected Given changed files (or the working-tree diff against HEAD by default), report the test fi Read git_context Show git context for the working tree: uncommitted changes annotated with index status, re Read impact Symbol-level blast radius: the transitive callers of a function or method as a pruned call

All 29 Local Rag tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Local Rag → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_annotation

What does the delete_annotation tool do? +

Remove an annotation that is no longer relevant — e.g. a bug that was fixed, a constraint that no longer applies, or a note on a deleted file/symbol. Use get_annotations first to find the annotation ID. It is categorised as a Destructive tool in the Local Rag 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 delete_annotation? +

Register the Local Rag MCP server in PolicyLayer and add a rule for delete_annotation: 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 Local Rag. Nothing to install.

What risk level is delete_annotation? +

delete_annotation 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 delete_annotation? +

Yes. Add a rate_limit block to the delete_annotation 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 delete_annotation completely? +

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

delete_annotation is provided by the Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Local Rag tool call.

Start from Local Rag, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.