delete_file

THE RISK

Critical Risk

Why delete_file needs a policy

This tool irreversibly removes data (a file) from a repository. Although severity is not critical (it affects a single file rather than the entire repository), the permanent nature of the deletion and the potential for an AI agent to accidentally or maliciously remove important source code, configuration files, or documentation warrants a 'high' severity rating.

From the tool's definition Tool description states: 'Delete a file from a GitHub repository. This is a destructive operation — the file will be permanently removed from the specified branch.' The word 'delete' combined with explicit acknowledgment that it is 'destructive' and…

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

POLICY

How to control delete_file

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

policy.json

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

delete_file 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 Gitbridge — 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 Gitbridge tools

Write add_issue_comment Add a comment to an existing GitHub Issue Write create_issue Create a new GitHub Issue in a repository Write create_repo Create a new GitHub repository on a personal account or within an organization Write flush_queue Commit all queued writes for a repository in a single GitHub commit. Call queue_write firs Write move_file Move or rename a file. Reads from old path, writes to new path, then returns a GitHub link Write push_multiple_files Create or update multiple files in a single commit using the Git Data API Write queue_write Queue a file write for batch commit. Writes are held in server memory and flushed together Write update_issue Update an existing GitHub Issue (change status, labels, title, or body)

All 16 Gitbridge 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 Gitbridge → 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_file

What does the delete_file tool do? +

Delete a file from a GitHub repository. This is a destructive operation — the file will be permanently removed from the specified branch. It is categorised as a Destructive tool in the Gitbridge 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_file? +

Register the Gitbridge MCP server in PolicyLayer and add a rule for delete_file: 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 Gitbridge. Nothing to install.

What risk level is delete_file? +

delete_file 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_file? +

Yes. Add a rate_limit block to the delete_file 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_file completely? +

Set action: deny in the PolicyLayer policy for delete_file. 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_file? +

delete_file is provided by the Gitbridge MCP server (iotus/gitbridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gitbridge tool call.

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

CHECK YOUR STACK →