delete_project_annotations

Batch delete ALL annotations for a specific project after successfully implementing all requested changes. CRITICAL WORKFLOW: Use this tool instead of individual delete_annotation calls when you have completed ALL annotation fixes for a project. This implements the efficient

Server Vibe Annotations Server vibe-annotations-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_project_annotations does on Vibe Annotations Server

AI agents call delete_project_annotations 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.

Why delete_project_annotations needs a policy

An AI agent that decides to call delete_project_annotations 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.

Questions about delete_project_annotations

What does the delete_project_annotations tool do? +

Batch delete ALL annotations for a specific project after successfully implementing all requested changes. CRITICAL WORKFLOW: Use this tool instead of individual delete_annotation calls when you have completed ALL annotation fixes for a project. This implements the efficient. 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.

How do I enforce a policy on delete_project_annotations? +

Register the Vibe Annotations Server MCP server in PolicyLayer and add a rule for delete_project_annotations: 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.

What risk level is delete_project_annotations? +

delete_project_annotations 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_project_annotations? +

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

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

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.