purge_cdn_cache

Purge CDN cache by URL

SERVER20i MCP Server SOURCEcbrown35/20i-mcp

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/cbrown35-20i-mcp/purge-cdn-cache.md

WHAT IT DOES

What purge_cdn_cache does on 20i MCP Server

AI agents call purge_cdn_cache to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why purge_cdn_cache is rated Critical

Purging CDN cache permanently removes cached data and cannot be undone; while the original content remains intact at origin, the cached copies are irrecoverably deleted and CDN performance may be temporarily degraded. This fits the Destructive category as the action cannot be reversed.

From the tool's definition 'Purge CDN cache' — purging a cache is an irreversible deletion of cached content, forcing re-fetching from origin

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs purge_cdn_cache safely

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

purge_cdn_cache Hidden

purge_cdn_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_cdn_cache"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about purge_cdn_cache

What does the purge_cdn_cache tool do? +

Purge CDN cache by URL. It is categorised as a Destructive tool in the 20i MCP Server 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_cache? +

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

What risk level is purge_cdn_cache? +

purge_cdn_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_cdn_cache? +

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

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

purge_cdn_cache is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server 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 →