Critical Risk →

cf_purge_cache_all

purge an entire zone (gated + confirm token).

Risk signalsBulk/mass operation — affects multiple targets

Part of the Seo Monster server.

cf_purge_cache_all can permanently delete data in Seo Monster, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SEO MONSTER →

Free to start. No card required.

AI agents may call cf_purge_cache_all to permanently remove or destroy resources in Seo Monster. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call cf_purge_cache_all in a loop, permanently destroying resources in Seo Monster. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cf_purge_cache_all"
  ]
}

See the full Seo Monster policy for all 39 tools.

Get this rule live on your own Seo Monster server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SEO MONSTER →

View all 39 tools →

These attack patterns abuse exactly the kind of access cf_purge_cache_all gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cf_purge_cache_all only ever does what you allow.

SECURE SEO MONSTER →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the cf_purge_cache_all tool do? +

purge an entire zone (gated + confirm token).. It is categorised as a Destructive tool in the Seo Monster 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 cf_purge_cache_all? +

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

What risk level is cf_purge_cache_all? +

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

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

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

cf_purge_cache_all is provided by the Seo Monster MCP server (pypi:seo-monster). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Seo Monster tool call.

Deterministic rules across all 39 Seo Monster tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.