delete_release_by_tag

Delete a release by tag 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-release-by-tag.md

WHAT IT DOES

What delete_release_by_tag does on Forgejo

AI agents call delete_release_by_tag 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_release_by_tag is rated Critical

Permanently removes release artifacts and cannot be undone; high blast radius in production repositories.

From the tool's definition delete release by tag name, irreversible removal

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_release_by_tag 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_release_by_tag, this is the rule to start with:

delete_release_by_tag Hidden

delete_release_by_tag 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_release_by_tag"
  ]
}

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_release_by_tag call is checked against it from then on.

FAQ

Questions about delete_release_by_tag

What does the delete_release_by_tag tool do? +

Delete a release by tag 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_release_by_tag? +

Register the Forgejo MCP server in PolicyLayer and add a rule for delete_release_by_tag: 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_release_by_tag? +

delete_release_by_tag 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_release_by_tag? +

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

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

delete_release_by_tag 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 →