New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gluecron_delete_file

Delete a file from a branch via git plumbing. Requires the existing blob sha (optimistic concurrency) and 'repo' scope. Mirrors DELETE /api/v2/contents.

SERVERGluecron SOURCEhttps://gluecron.com/mcp
Critical RISK CLASS
Category Destructive
Parameters 66 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-gluecron-gluecron/gluecron-delete-file.md

What gluecron_delete_file does on Gluecron

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

ParameterTypeRequiredDescription
sha string Yes Current blob sha (40-hex)
path string Yes
repo string Yes
owner string Yes
branch string Yes
message string Yes

Parameters from the server's own tool schema.

Why gluecron_delete_file is rated Critical

This tool irreversibly deletes files from a git repository. Deletion of repository files cannot be undone without access to git history recovery mechanisms, and represents permanent loss of data. While git has reflog capabilities, from the perspective of the repository's current state, this action is destructive.

From the tool's definition Delete a file from a branch via git plumbing...Mirrors DELETE /api/v2/contents.

Risk signalsAccepts file system path (path)

Questions about gluecron_delete_file

What does the gluecron_delete_file tool do? +

Delete a file from a branch via git plumbing. Requires the existing blob sha (optimistic concurrency) and 'repo' scope. Mirrors DELETE /api/v2/contents. It is categorised as a Destructive tool in the Gluecron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does gluecron_delete_file accept? +

gluecron_delete_file accepts 6 parameters: sha, path, repo, owner, branch, message. Required: sha, path, repo, owner, branch, message. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gluecron_delete_file? +

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

What risk level is gluecron_delete_file? +

gluecron_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 gluecron_delete_file? +

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

Set action: deny in the PolicyLayer policy for gluecron_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 gluecron_delete_file? +

gluecron_delete_file is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Gluecron, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gluecron's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.