queue_cleanup
Clean up old changes based on retention policy (approved: 30 days, rejected: 7 days, applied: 90 days).
This record as markdown: /tools/vamerli-elementify-mcp/queue-cleanup.md
What queue_cleanup does on Elementify MCP
AI agents call queue_cleanup 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 queue_cleanup is rated Critical
Cleanup operations that purge records based on retention policies are typically irreversible deletions. The tool removes approved, rejected, and applied changes permanently once they exceed their retention period. This cannot be undone once executed, making it Destructive.
From the tool's definition 'Clean up old changes' based on retention policy implies permanent deletion of records older than specified thresholds (30, 7, 90 days)
Attacks that exploit this kind of access
The rule that runs queue_cleanup 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 queue_cleanup, this is the rule to start with:
queue_cleanup 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 queue_cleanup call is checked against it from then on.
Questions about queue_cleanup
Clean up old changes based on retention policy (approved: 30 days, rejected: 7 days, applied: 90 days). 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 queue_cleanup: 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.
queue_cleanup 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 queue_cleanup 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 queue_cleanup. 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.
queue_cleanup 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