remove_project

Remove one of the authenticated user's projects. PlugLayer removes the project's apps first, then tears down the project and archives the record for recovery/history.

Server PlugLayer MCP Server pluglayer/mcp
Category Destructive
Risk class Critical
Parameters 00 required

What remove_project does on PlugLayer MCP Server

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

Why remove_project needs a policy

This tool permanently removes infrastructure (project and apps) rather than merely modifying or updating it. Although PlugLayer archives the record, the live project and its resources are destroyed. This is irreversible and constitutes a destructive operation.

From the tool's definition 'Remove one of the authenticated user's projects' and 'tears down the project' - the tool irreversibly deletes a project and its associated apps, which cannot be undone (only archived for recovery).

Questions about remove_project

What does the remove_project tool do? +

Remove one of the authenticated user's projects. PlugLayer removes the project's apps first, then tears down the project and archives the record for recovery/history. 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.

How do I enforce a policy on remove_project? +

Register the PlugLayer MCP Server MCP server in PolicyLayer and add a rule for remove_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.

What risk level is remove_project? +

remove_project 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 remove_project? +

Yes. Add a rate_limit block to the remove_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.

How do I block remove_project completely? +

Set action: deny in the PolicyLayer policy for remove_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.

What MCP server provides remove_project? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.