Revoke an issued certificate.
AI agents call gandi_cert_revoke to permanently remove resources in Gandi — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Certificate revocation is a destructive action that permanently invalidates a certificate's trust status. Once revoked, the certificate cannot be reinstated—it must be reissued from scratch. This is irreversible and has significant operational impact (services relying on the cert will fail). While not as severe as deletion, revocation is the functional equivalent of destroying the certificate's utility.
From the tool's definition Tool name 'gandi_cert_revoke' and description 'Revoke an issued certificate' indicate irreversible revocation of a certificate, which cannot be undone without reissuing.
Attacks that exploit this kind of access
Revoke an issued certificate. It is categorised as a Destructive tool in the Gandi MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gandi MCP server in PolicyLayer and add a rule for gandi_cert_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 Gandi. Nothing to install.
gandi_cert_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 gandi_cert_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 gandi_cert_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.
gandi_cert_revoke is provided by the Gandi MCP server (millsymills-com/gandi-mcp). 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 →