delete_project

THE RISK

Critical Risk

Why delete_project needs a policy

Deleting a project is a destructive action that permanently removes code, issues, pull requests, and all associated data from GitHub or GitLab. This operation cannot be reversed and has significant blast radius if an AI agent misuses it. Destructive is more severe than Write or Execute, so it takes precedence.

From the tool's definition Tool name is 'delete_project' with description 'Delete a project from the specified platform' — uses the word 'Delete' indicating an irreversible operation that cannot be undone.

Documented attack patterns abuse exactly the kind of access delete_project gives an agent:

POLICY

How to control delete_project

PolicyLayer is an MCP gateway — it sits between your AI agents and Git MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_project:

policy.json

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

delete_project disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Git MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Git MCP Server tools

Destructive close_merge_request close_merge_request Write close_issue Close an issue Write close_milestone Close a milestone Write create_fork create_fork Write create_issue Create a new issue in a project Write create_issue_comment Create a comment on an issue Write create_merge_request create_merge_request Write create_milestone Create a new milestone in a project. due_date format: YYYY-MM-DD

All 33 Git MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Git MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_project

What does the delete_project tool do? +

Delete a project from the specified platform. It is categorised as a Destructive tool in the Git 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 Git 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 Git 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 Git MCP Server MCP server (yumeminami/git_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Git MCP Server tool call.

Start from Git MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →