fort_cache_purge

Purge the fort

SERVERWordpress SOURCE@cavort-it-systems/wordpress-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/io-github-cvrt-jh-wordpress-mcp/fort-cache-purge.md

WHAT IT DOES

What fort_cache_purge does on Wordpress

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

RISK

Why fort_cache_purge is rated Critical

Purging cache destroys cached state irreversibly, blocking recovery without rebuilding.

From the tool's definition Purge the fort - irreversibly clears cached data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fort_cache_purge safely

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

fort_cache_purge Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about fort_cache_purge

What does the fort_cache_purge tool do? +

Purge the fort. It is categorised as a Destructive tool in the Wordpress 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 fort_cache_purge? +

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

What risk level is fort_cache_purge? +

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

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

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

fort_cache_purge is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress 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 →