Delete a project.
AI agents call project_delete to permanently remove resources in Semaphore — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a project is an irreversible action that destroys the project and its associated data. This cannot be undone through the tool itself. The blast radius is significant in a workflow automation context, as it eliminates infrastructure-as-code configurations, task definitions, and automation state. This is categorized as Destructive rather than Write, as it is not reversible or merely modifying data.
From the tool's definition Tool name is 'project_delete' and description states 'Delete a project.' The verb 'delete' combined with the irreversible nature of removing a project (which contains automation workflows, tasks, templates, and inventory) indicates a destructive operation.
Attacks that exploit this kind of access
Delete a project. It is categorised as a Destructive tool in the Semaphore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Semaphore MCP server in PolicyLayer and add a rule for project_delete: 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 Semaphore. Nothing to install.
project_delete 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 project_delete 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 project_delete. 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.
project_delete is provided by the Semaphore MCP server (vitexsoftware/semaphore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →