delete_repo_action_secret

Delete an Actions secret of a repository

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-repo-action-secret.md

WHAT IT DOES

What delete_repo_action_secret does on Forgejo

AI agents call delete_repo_action_secret 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_repo_action_secret is rated Critical

Permanently removes repository secrets; cannot be undone and breaks CI/CD workflows.

From the tool's definition Delete an Actions secret of a repository

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_repo_action_secret Hidden

delete_repo_action_secret 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_repo_action_secret"
  ]
}

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

FAQ

Questions about delete_repo_action_secret

What does the delete_repo_action_secret tool do? +

Delete an Actions secret of a repository. 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_repo_action_secret? +

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

delete_repo_action_secret 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_repo_action_secret? +

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

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

delete_repo_action_secret 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

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

Guides

Govern database agents →Blast radius →Tool call approval →