github_delete_secret

Delete a repo secret.

SERVERGithub SOURCEdkeeno/github-mcp-server

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/dkeeno-github-mcp-server/github-delete-secret.md

WHAT IT DOES

What github_delete_secret does on Github

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

RISK

Why github_delete_secret is rated Critical

This tool permanently removes secrets from a repository configuration. Secrets in GitHub are sensitive credentials and API keys used for authentication and access control. Deletion cannot be undone without manual recreation, and an unauthorized deletion could break CI/CD pipelines, authentication workflows, or expose services to downtime.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a repo secret' — irreversible removal of stored sensitive data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_delete_secret safely

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

github_delete_secret Hidden

github_delete_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": [
    "github_delete_secret"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about github_delete_secret

What does the github_delete_secret tool do? +

Delete a repo secret. It is categorised as a Destructive tool in the Github 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 github_delete_secret? +

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

What risk level is github_delete_secret? +

github_delete_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 github_delete_secret? +

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

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

github_delete_secret is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 69 Github 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 →