infra.cloudflare.purge_cache

⚡ ACTION: Purge Cloudflare CDN cache — all cached files or specific URLs (max 30). Forces CDN to fetch fresh content from origin server (Cloudflare)

SERVERApibase SOURCEapibase-mcp-client

Critical RISK CLASS

Category Destructive

Parameters 31 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/infra.cloudflare.purge-cache.md

WHAT IT DOES

What infra.cloudflare.purge_cache does on Apibase

AI agents call infra.cloudflare.purge_cache to permanently remove resources in Apibase, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`files`	array	—	Specific URLs to purge (max 30)
`zone_id`	string	Yes	Cloudflare Zone ID
`purge_everything`	boolean	—	Purge all cached files (default false)

Parameters from the server's own tool schema.

RISK

Why infra.cloudflare.purge_cache is rated Critical

Irreversibly purges CDN cache, forcing origin fetches and potentially causing outages.

From the tool's definition Purge Cloudflare CDN cache — all cached files or specific URLs

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infra.cloudflare.purge_cache safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infra.cloudflare.purge_cache, this is the rule to start with:

infra.cloudflare.purge_cache Hidden

infra.cloudflare.purge_cache 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": [
    "infra.cloudflare.purge_cache"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every infra.cloudflare.purge_cache call is checked against it from then on.

FAQ

Questions about infra.cloudflare.purge_cache

What does the infra.cloudflare.purge_cache tool do? +

⚡ ACTION: Purge Cloudflare CDN cache — all cached files or specific URLs (max 30). Forces CDN to fetch fresh content from origin server (Cloudflare). It is categorised as a Destructive tool in the Apibase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does infra.cloudflare.purge_cache accept? +

infra.cloudflare.purge_cache accepts 3 parameters: files, zone_id, purge_everything. Required: zone_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on infra.cloudflare.purge_cache? +

Register the Apibase MCP server in PolicyLayer and add a rule for infra.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 Apibase. Nothing to install.

What risk level is infra.cloudflare.purge_cache? +

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

Can I rate-limit infra.cloudflare.purge_cache? +

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

How do I block infra.cloudflare.purge_cache completely? +

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

What MCP server provides infra.cloudflare.purge_cache? +

infra.cloudflare.purge_cache is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →