Revoke one CI/OIDC deploy binding. Revocation stops future CI gateway requests, but does not undo already deployed releases or rotate secrets.
AI agents call ci_revoke_binding to permanently remove resources in Run402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking a CI/OIDC binding is an irreversible removal of an authorization binding. While it doesn't delete data or rotate secrets, it permanently removes the binding itself — future CI deployments will fail until a new binding is explicitly created. This is a destructive, non-reversible configuration change with high blast radius since it can break automated deployment pipelines.
From the tool's definition 'Revoke one CI/OIDC deploy binding. Revocation stops future CI gateway requests' — revoking a binding is an irreversible access-control action that cannot be undone (a new binding would need to be created), permanently blocking future CI deployments through…
Attacks that exploit this kind of access
Revoke one CI/OIDC deploy binding. Revocation stops future CI gateway requests, but does not undo already deployed releases or rotate secrets. It is categorised as a Destructive tool in the Run402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for ci_revoke_binding: 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 Run402. Nothing to install.
ci_revoke_binding 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 ci_revoke_binding 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 ci_revoke_binding. 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.
ci_revoke_binding is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →