secret-delete

Deletes a repository, organization, or environment GitHub Actions secret.

SERVERGit SOURCEDave-London/Pare

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/io-github-dave-london-git/secret-delete.md

WHAT IT DOES

What secret-delete does on Git

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

RISK

Why secret-delete is rated Critical

This tool permanently removes GitHub Actions secrets, which cannot be undone. Deletion of secrets is an irreversible destructive action with potential blast radius if an AI agent mistakenly deletes critical authentication or deployment credentials. This is more severe than a Write operation and falls clearly into the Destructive category.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Deletes a repository, organization, or environment GitHub Actions secret' - this is an irreversible operation that removes sensitive configuration data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs secret-delete safely

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

secret-delete Hidden

secret-delete 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": [
    "secret-delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about secret-delete

What does the secret-delete tool do? +

Deletes a repository, organization, or environment GitHub Actions secret. It is categorised as a Destructive tool in the Git 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 secret-delete? +

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

What risk level is secret-delete? +

secret-delete 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 secret-delete? +

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

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

secret-delete is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git 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 code and CI agents →Blast radius →Tool call approval →