delete_cdn_ssl_certificate
Remove SSL certificate from a CDN zone.
This record as markdown: /tools/rsp2k-mcp-vultr/delete-cdn-ssl-certificate.md
What delete_cdn_ssl_certificate does on Vultr MCP
AI agents call delete_cdn_ssl_certificate to permanently remove resources in Vultr MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_cdn_ssl_certificate is rated Critical
Deleting an SSL certificate from a CDN zone is a destructive, non-reversible action that cannot be undone programmatically. If an AI agent executes this without proper intent, it removes critical encryption infrastructure, breaking HTTPS for end users and exposing traffic. High severity due to infrastructure impact and inability to recover without manual re-issuance.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Remove SSL certificate' — irreversible deletion of security infrastructure.
Attacks that exploit this kind of access
The rule that runs delete_cdn_ssl_certificate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_cdn_ssl_certificate, this is the rule to start with:
delete_cdn_ssl_certificate 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 Vultr MCP, apply this rule, and every delete_cdn_ssl_certificate call is checked against it from then on.
Questions about delete_cdn_ssl_certificate
Remove SSL certificate from a CDN zone. It is categorised as a Destructive tool in the Vultr MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vultr MCP server in PolicyLayer and add a rule for delete_cdn_ssl_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 Vultr MCP. Nothing to install.
delete_cdn_ssl_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_cdn_ssl_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_cdn_ssl_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_cdn_ssl_certificate is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
Across the catalogue