Remove expired acknowledged events from the queue to free space
AI agents call prune_events to permanently remove resources in ClawDaemon MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes event records from a persistent daemon system that handles automation, webhooks, and messaging across 23 platforms. Once events are pruned, they cannot be recovered. While the deletion targets 'expired' events (suggesting a maintenance operation), the irreversible nature of removing data from a critical automation queue makes this Destructive rather than Write.
From the tool's definition Tool name 'prune_events' with description 'Remove expired acknowledged events from the queue' indicates irreversible deletion of data records.
Attacks that exploit this kind of access
Remove expired acknowledged events from the queue to free space. It is categorised as a Destructive tool in the ClawDaemon MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ClawDaemon MCP server in PolicyLayer and add a rule for prune_events: 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 ClawDaemon MCP. Nothing to install.
prune_events 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 prune_events 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 prune_events. 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.
prune_events is provided by the ClawDaemon MCP server (mordiaky/clawdaemon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →