Delete an SSL certificate from a site
AI agents call delete_certificate to permanently remove resources in Ploi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes an SSL certificate from a site. Deletion of certificates is an unrecoverable action that requires manual recreation. While not directly causing data loss, it removes critical security infrastructure and could cause service disruption or security vulnerabilities.
From the tool's definition Tool name is 'delete_certificate' with description 'Delete an SSL certificate from a site'. The verb 'delete' indicates irreversible removal of an SSL certificate, which cannot be undone without recreating it.
Attacks that exploit this kind of access
Delete an SSL certificate from a site. It is categorised as a Destructive tool in the Ploi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ploi MCP Server MCP server in PolicyLayer and add a rule for delete_certificate: 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 Ploi MCP Server. Nothing to install.
delete_certificate 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 delete_certificate 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 delete_certificate. 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.
delete_certificate is provided by the Ploi MCP Server MCP server (sudanese/ploi-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 →