Alias for remove_project().
AI agents call delete_project to permanently remove resources in PlugLayer MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes an entire project, which cannot be undone. It represents a destructive action with significant blast radius in an infrastructure management context—removing a project likely cascades deletion of associated resources, deployments, and data. Even if an AI agent is given legitimate infrastructure management authority, accidental project deletion would be catastrophic.
From the tool's definition Tool name is 'delete_project' with description stating it is an 'Alias for remove_project()'. The verb 'delete' combined with 'project' indicates irreversible removal of infrastructure/data.
Attacks that exploit this kind of access
Alias for remove_project(). It is categorised as a Destructive tool in the PlugLayer MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PlugLayer MCP Server MCP server in PolicyLayer and add a rule for delete_project: 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 PlugLayer MCP Server. Nothing to install.
delete_project 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_project 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_project. 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_project is provided by the PlugLayer MCP Server MCP server (pluglayer/mcp). 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 →