delete_project

Delete a project

SERVERNitrostack SOURCEnitrocloudofficial/nitrostack

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nitrostack/delete-project.md

WHAT IT DOES

What delete_project does on Nitrostack

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

RISK

Why delete_project is rated Critical

This tool permanently removes a project and cannot be undone. Deletion is irreversible and represents a complete loss of project data. This is the most severe category applicable (Destructive > Execute > Write > Read). The high severity reflects the significant blast radius if an AI agent mistakenly deletes an important project.

From the tool's definition Tool name is 'delete_project' with description 'Delete a project'. The verb 'delete' combined with the scope 'project' indicates irreversible removal of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_project safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, 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 Hidden

delete_project is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_project"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every delete_project call is checked against it from then on.

FAQ

Questions about delete_project

What does the delete_project tool do? +

Delete a project. It is categorised as a Destructive tool in the Nitrostack 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 Nitrostack 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 Nitrostack. 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 Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nitrostack, and thousands of servers like it.

This server

All 697 Nitrostack tools → Critical-risk tools on this server →

Across the catalogue

clear_project_index on ACE-MCP →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →