Delete a file from a GitHub repository.
AI agents call deleteFile to permanently remove resources in GitHub MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a file is an irreversible operation that cannot be undone through the tool's normal operation. Even though GitHub maintains version history, the deletion itself is a destructive action that removes the file from the current state of the repository.
From the tool's definition Tool name 'deleteFile' with description 'Delete a file from a GitHub repository' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a file from a GitHub repository. It is categorised as a Destructive tool in the GitHub MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for deleteFile: 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 GitHub MCP Server. Nothing to install.
deleteFile 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 deleteFile 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 deleteFile. 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.
deleteFile is provided by the GitHub MCP Server MCP server (j-nowcow/github-mcp-practice). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →