Purge Cloudflare cache for the configured zone
AI agents call cloudflare_purge_cache to permanently remove resources in VibeServe — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cache purging cannot be undone; once purged, cached content is gone and must be rebuilt organically or via re-warming. A misuse could cause significant performance degradation, increased origin load, and potential service disruption for production traffic. This qualifies as Destructive given the irreversible nature of the operation.
From the tool's definition 'Purge Cloudflare cache' — purging a cache is an irreversible operation that destroys cached content for the configured zone, forcing all assets to be re-fetched from origin.
Attacks that exploit this kind of access
Purge Cloudflare cache for the configured zone. It is categorised as a Destructive tool in the VibeServe MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the VibeServe MCP server in PolicyLayer and add a rule for cloudflare_purge_cache: 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 VibeServe. Nothing to install.
cloudflare_purge_cache 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 cloudflare_purge_cache 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 cloudflare_purge_cache. 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.
cloudflare_purge_cache is provided by the VibeServe MCP server (ncsound919/vibeserve). 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 →