Purge all Cloudflare CDN cached content for a site
AI agents call sitebay_clear_cache to permanently remove resources in SiteBay MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Purging CDN cache is an irreversible operation that immediately removes all cached content, forcing origin servers to rebuild cache from scratch. This can cause significant performance degradation and increased origin load for high-traffic sites, and the purged cache cannot be restored. The word 'purge' and 'all' indicate a broad, non-selective destructive action.
From the tool's definition Purge all Cloudflare CDN cached content for a site
Attacks that exploit this kind of access
Purge all Cloudflare CDN cached content for a site. It is categorised as a Destructive tool in the SiteBay MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_clear_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 SiteBay MCP Server. Nothing to install.
sitebay_clear_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 sitebay_clear_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 sitebay_clear_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.
sitebay_clear_cache is provided by the SiteBay MCP Server MCP server (sitebay/sitebay-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 →