delete_project
PERMANENTLY delete a DenkOps deployment and ALL its data (containers, images, volume, and records). Cannot be undone. Requires confirm set to the project's exact slug; call with an empty confirm first to see the confirmation instruction.
This record as markdown: /tools/denkopsai-mcp/delete-project.md
What delete_project does on Denkopsai
AI agents call delete_project to permanently remove resources in Denkopsai, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | string | — | The project's exact slug, to confirm permanent deletion |
project_id | string | Yes |
Parameters from the server's own tool schema.
Why delete_project is rated Critical
This tool irreversibly deletes entire deployments and associated data with no recovery mechanism. The blast radius is maximal—all containers, images, volumes, and records are lost permanently. This is the most severe category (Destructive) and warrants critical severity due to the total and permanent nature of the operation.
From the tool's definition Tool description explicitly states: 'PERMANENTLY delete a DenkOps deployment and ALL its data (containers, images, volume, and records).
Attacks that exploit this kind of access
The rule that runs delete_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_project, this is the rule to start with:
delete_project is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every delete_project call is checked against it from then on.
Questions about delete_project
PERMANENTLY delete a DenkOps deployment and ALL its data (containers, images, volume, and records). Cannot be undone. Requires confirm set to the project's exact slug; call with an empty confirm first to see the confirmation instruction. It is categorised as a Destructive tool in the Denkopsai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_project accepts 2 parameters: confirm, project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai 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 Denkopsai. 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 Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
Across the catalogue