secret-delete
Deletes a repository, organization, or environment GitHub Actions secret.
This record as markdown: /tools/io-github-dave-london-pare-search/secret-delete.md
What secret-delete does on Search
AI agents call secret-delete to permanently remove resources in Search, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why secret-delete is rated Critical
This tool irreversibly deletes GitHub Actions secrets, which cannot be undone. Deletion of secrets is a destructive operation with high blast radius—accidental or malicious deletion could compromise authentication, expose infrastructure access, or break CI/CD pipelines. This is clearly Destructive rather than Write because the action cannot be reversed.
From the tool's definition Tool name 'secret-delete' and description 'Deletes a repository, organization, or environment GitHub Actions secret' explicitly indicate irreversible deletion of secrets.
Attacks that exploit this kind of access
The rule that runs secret-delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, 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 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Search, apply this rule, and every secret-delete call is checked against it from then on.
Questions about secret-delete
Deletes a repository, organization, or environment GitHub Actions secret. It is categorised as a Destructive tool in the Search MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Search 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 Search. Nothing to install.
secret-delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
secret-delete is provided by the Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Search, and thousands of servers like it.
Across the catalogue