purge_cdn_zone

Purge all cached content from a CDN zone.

SERVERVultr MCP SOURCErsp2k/mcp-vultr

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rsp2k-mcp-vultr/purge-cdn-zone.md

WHAT IT DOES

What purge_cdn_zone does on Vultr MCP

AI agents call purge_cdn_zone 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.

RISK

Why purge_cdn_zone is rated Critical

The 'purge' operation removes cached content from a CDN zone, which is an irreversible action that cannot be undone. While not data deletion per se, it destroys the cached state and forces regeneration, making it destructive in nature. The broad scope ('all cached content') and potential service impact (cache miss spike, performance degradation) justify 'high' severity.

From the tool's definition Tool name 'purge_cdn_zone' and description 'Purge all cached content from a CDN zone' explicitly indicate irreversible removal of cached data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs purge_cdn_zone 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 purge_cdn_zone, this is the rule to start with:

purge_cdn_zone Hidden

purge_cdn_zone is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "purge_cdn_zone"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every purge_cdn_zone call is checked against it from then on.

FAQ

Questions about purge_cdn_zone

What does the purge_cdn_zone tool do? +

Purge all cached content 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.

How do I enforce a policy on purge_cdn_zone? +

Register the Vultr MCP server in PolicyLayer and add a rule for purge_cdn_zone: 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.

What risk level is purge_cdn_zone? +

purge_cdn_zone is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit purge_cdn_zone? +

Yes. Add a rate_limit block to the purge_cdn_zone 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.

How do I block purge_cdn_zone completely? +

Set action: deny in the PolicyLayer policy for purge_cdn_zone. 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.

What MCP server provides purge_cdn_zone? +

purge_cdn_zone 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.

KEEP EXPLORING

More on Vultr, and thousands of servers like it.

This server

All 284 Vultr tools → Critical-risk tools on this server →

Across the catalogue

archive_purge on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →