Critical Risk →

wordpress_cleanup_database

wordpress_cleanup_database

How to control wordpress_cleanup_database ↓

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

Critical Risk

Database cleanup operations typically involve permanently deleting orphaned records, post revisions, transients, spam comments, and other data that cannot be easily recovered. The 'cleanup' operation is generally irreversible without a prior backup. The description is empty, which lowers confidence slightly, but the name strongly implies destructive behavior.

From the tool's definition Tool name 'wordpress_cleanup_database' implies irreversible removal or purging of database records; sibling tools include 'wordpress_backup_database' and 'wordpress_bulk_delete_media', suggesting destructive operations are common on this server.

Documented attack patterns abuse exactly the kind of access wordpress_cleanup_database gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wordpress_cleanup_database:

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

wordpress_cleanup_database disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register WordPress MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the wordpress_cleanup_database tool do? +

wordpress_cleanup_database. It is categorised as a Destructive tool in the WordPress 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 wordpress_cleanup_database? +

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

What risk level is wordpress_cleanup_database? +

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

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

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

wordpress_cleanup_database is provided by the WordPress MCP Server MCP server (raheesahmed/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WordPress MCP Server tool call.

Deterministic rules across all 190 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

190 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.