Critical Risk →

onui_delete_annotation

Delete a single annotation by id.

How to control onui_delete_annotation ↓

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

Critical Risk

This tool permanently removes annotations without a stated undo mechanism. While the blast radius is limited to annotation data (not financial or system-critical), deletion is irreversible and destructive in nature, making it more severe than Write operations. An AI agent could maliciously or accidentally purge important UI annotations, hindering team workflows.

From the tool's definition Tool name contains 'delete' and description states 'Delete a single annotation by id' — an irreversible operation that removes data.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "onui_delete_annotation"
  ]
}

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

  1. Create a free account and register onUI — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the onui_delete_annotation tool do? +

Delete a single annotation by id. It is categorised as a Destructive tool in the onUI 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 onui_delete_annotation? +

Register the onUI MCP server in PolicyLayer and add a rule for onui_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 onUI. Nothing to install.

What risk level is onui_delete_annotation? +

onui_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 onui_delete_annotation? +

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

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

onui_delete_annotation is provided by the onUI MCP server (onllm-dev/onui). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every onUI tool call.

Deterministic rules across all 8 onUI tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

8 onUI tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.