clean_database
Clean database bloat: revisions, expired transients, spam comments. L2 governance: auto-queues changes.
This record as markdown: /tools/vamerli-elementify-mcp/clean-database.md
What clean_database does on Elementify MCP
AI agents call clean_database to permanently remove resources in Elementify MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clean_database is rated Critical
Cleaning database bloat involves irreversible deletion of data such as post revisions, expired transients, and spam comments. These operations purge records from the database permanently. Even though these items may seem low-value, deleting revisions removes version history and spam purges could affect legitimate content misclassified as spam. The blast radius is high as it operates on the entire WordPress database.
From the tool's definition 'Clean database bloat: revisions, expired transients, spam comments' — permanently removes database records (revisions, transients, spam) that cannot be recovered once deleted.
Attacks that exploit this kind of access
The rule that runs clean_database safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clean_database, this is the rule to start with:
clean_database is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every clean_database call is checked against it from then on.
Questions about clean_database
Clean database bloat: revisions, expired transients, spam comments. L2 governance: auto-queues changes. It is categorised as a Destructive tool in the Elementify MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Elementify MCP server in PolicyLayer and add a rule for clean_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 Elementify MCP. Nothing to install.
clean_database is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clean_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.
Set action: deny in the PolicyLayer policy for clean_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.
clean_database is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elementify, and thousands of servers like it.
Across the catalogue