purge_cache

Purge Cloudflare cache

SERVERNcp SOURCE@portel/ncp

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/io-github-portel-dev-ncp/purge-cache.md

WHAT IT DOES

What purge_cache does on Ncp

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

RISK

Why purge_cache is rated Critical

Purging a cache is a destructive action that cannot be easily undone—cached content is removed and will need to be re-fetched and regenerated, potentially causing service disruptions or performance degradation. While not as severe as deleting persistent data, purging production cache is a high-risk operation that can significantly impact availability and user experience.

From the tool's definition Tool name is 'purge_cache' with description 'Purge Cloudflare cache'. The verb 'purge' indicates irreversible deletion or clearing of cached data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs purge_cache safely

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

purge_cache Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about purge_cache

What does the purge_cache tool do? +

Purge Cloudflare cache. It is categorised as a Destructive tool in the Ncp 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_cache? +

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

What risk level is purge_cache? +

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 purge_cache? +

Yes. Add a rate_limit block to the 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 purge_cache completely? +

Set action: deny in the PolicyLayer policy for 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 purge_cache? +

purge_cache is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp 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 code and CI agents →Blast radius →Tool call approval →