Permanently removes a specific annotation after successfully implementing the requested change or fix. IMPORTANT: Consider using delete_project_annotations for batch deletion when implementing multiple fixes. Use this individual deletion tool when: (1) You have successfully implemented a single a...
AI agents call delete_annotation to permanently remove resources in Vibe Annotations Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call delete_annotation doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Vibe Annotations Server is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Permanently removes a specific annotation after successfully implementing the requested change or fix. IMPORTANT: Consider using delete_project_annotations for batch deletion when implementing multiple fixes. Use this individual deletion tool when: (1) You have successfully implemented a single annotation fix, (2) You prefer to delete annotations one-by-one as you implement them, (3) You are working on just one annotation. For efficiency when handling multiple annotations, use delete_project_annotations instead. The deletion is irreversible and removes the annotation from both extension storage and MCP data. NEVER delete annotations that still need work, contain unaddressed feedback, or serve as ongoing reminders. It is categorised as a Destructive tool in the Vibe Annotations Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vibe Annotations Server 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 Vibe Annotations Server. Nothing to install.
delete_annotation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
delete_annotation is provided by the Vibe Annotations Server MCP server (vibe-annotations-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.