This record as markdown: /tools/delimit/delimit-secret-revoke.md
What delimit_secret_revoke does on Delimit
AI agents call delimit_secret_revoke to permanently remove resources in Delimit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delimit_secret_revoke is rated Critical
Revoking a secret (API key, token, credential) is an irreversible destructive action — once revoked, dependent services or agents relying on that secret will lose access and the secret cannot be 'un-revoked'. The description is empty, so classification is based on the name alone, but 'revoke' in a secrets management context is unambiguous.
From the tool's definition Tool name 'delimit_secret_revoke' — 'revoke' strongly implies irreversible invalidation of a secret/credential.
Attacks that exploit this kind of access
The rule that runs delimit_secret_revoke safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delimit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delimit_secret_revoke, this is the rule to start with:
delimit_secret_revoke 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 Delimit, apply this rule, and every delimit_secret_revoke call is checked against it from then on.
Questions about delimit_secret_revoke
delimit_secret_revoke is a destructive tool on the Delimit MCP server. It is categorised as a Destructive tool in the Delimit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Delimit MCP server in PolicyLayer and add a rule for delimit_secret_revoke: 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 Delimit. Nothing to install.
delimit_secret_revoke 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 delimit_secret_revoke 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 delimit_secret_revoke. 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.
delimit_secret_revoke is provided by the Delimit MCP server (delimit-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delimit, and thousands of servers like it.
Across the catalogue