create_cdn_ssl_certificate
A write tool on the Vultr MCP server.
This record as markdown: /tools/rsp2k-mcp-vultr/create-cdn-ssl-certificate.md
What create_cdn_ssl_certificate does on Vultr MCP
AI agents use create_cdn_ssl_certificate to create or update resources in Vultr MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vultr MCP environment.
Why create_cdn_ssl_certificate is rated Medium
This tool creates a new SSL certificate, which is a reversible Write operation. While SSL certificates are security-sensitive resources, creating one is not inherently destructive, financial, or code-execution in nature. The moderate severity reflects that misconfiguration could expose CDN endpoints to security risks or cause service disruption, but the action itself is reversible via deletion.
From the tool's definition Tool name 'create_cdn_ssl_certificate' indicates creation of a new SSL certificate resource for CDN infrastructure. The verb 'create' explicitly signals a Write operation that adds a new resource to the system.
Attacks that exploit this kind of access
The rule that runs create_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 create_cdn_ssl_certificate, this is the rule to start with:
create_cdn_ssl_certificate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every create_cdn_ssl_certificate call is checked against it from then on.
Questions about create_cdn_ssl_certificate
create_cdn_ssl_certificate is a write tool on the Vultr MCP server. It is categorised as a Write tool in the Vultr MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vultr MCP server in PolicyLayer and add a rule for create_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.
create_cdn_ssl_certificate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
This server
Across the catalogue