delete_push_mirror

Remove a push mirror from a repository by its remote name

SERVERForgejo SOURCEsqcows/forgejo-mcp

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/sqcows-forgejo-mcp/delete-push-mirror.md

WHAT IT DOES

What delete_push_mirror does on Forgejo

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

RISK

Why delete_push_mirror is rated Critical

Deletion of repository push mirrors is irreversible and breaks repository synchronization.

From the tool's definition Remove a push mirror from a repository; irreversible deletion operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_push_mirror safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_push_mirror, this is the rule to start with:

delete_push_mirror Hidden

delete_push_mirror 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_push_mirror"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_push_mirror

What does the delete_push_mirror tool do? +

Remove a push mirror from a repository by its remote name. It is categorised as a Destructive tool in the Forgejo 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_push_mirror? +

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

What risk level is delete_push_mirror? +

delete_push_mirror 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_push_mirror? +

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

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

delete_push_mirror is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →