mcp_flush_cache

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/mcp-flush-cache.md

WHAT IT DOES

What mcp_flush_cache does on Wordpress

AI agents call mcp_flush_cache 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 mcp_flush_cache is rated Critical

Irreversibly deletes all cached data and transients, potentially causing performance degradation.

From the tool's definition Flush the WordPress object cache and delete all transients

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_flush_cache 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 mcp_flush_cache, this is the rule to start with:

mcp_flush_cache Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mcp_flush_cache

What does the mcp_flush_cache tool do? +

Flush the WordPress object cache and delete all transients and site transients. Does NOT purge a page cache in front of WordPress (Bearfort forts: the nginx page cache is purged by bearfort-cache.php on content changes; a manual purge goes through the Bearfort API, not this tool). 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 mcp_flush_cache? +

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

What risk level is mcp_flush_cache? +

mcp_flush_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 mcp_flush_cache? +

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

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

mcp_flush_cache 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

reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

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