delete_project

Delete a project. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.

Server Coolify MCP Server kof70/coolify-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_project does on Coolify MCP Server

AI agents call delete_project to permanently remove resources in Coolify MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_project needs a policy

Deleting a project in a PaaS platform is inherently destructive—it removes project configurations, associated applications, databases, and deployments that cannot be recovered. This represents the highest severity misuse risk: an AI agent with access to this tool could permanently destroy infrastructure and data. The confirmation mechanism acknowledges the irreversible nature of the operation.

From the tool's definition Tool name 'delete_project' combined with description stating it 'Delete a project' indicates irreversible deletion of data. The mention of a confirmation requirement (confirm: true parameter) further confirms this is a destructive action that cannot be undone.

Questions about delete_project

What does the delete_project tool do? +

Delete a project. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter. It is categorised as a Destructive tool in the Coolify 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 delete_project? +

Register the Coolify 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 Coolify MCP Server. Nothing to install.

What risk level is delete_project? +

delete_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 delete_project? +

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.

How do I block delete_project completely? +

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.

What MCP server provides delete_project? +

delete_project is provided by the Coolify MCP Server MCP server (kof70/coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

delete_project is one line of Coolify MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.