Remove old task artifact directories by age, with dry-run support by default.
AI agents call prune_task_artifacts to permanently remove resources in JS Reverse MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting directories is a destructive, irreversible operation. Although dry-run support mitigates risk, the tool's core function is to permanently remove data without recovery. High severity due to potential loss of task state, logs, or build artifacts that may be needed for debugging or recovery.
From the tool's definition Tool explicitly 'remove[s]' artifact directories; operation is irreversible deletion of files/data based on age criteria.
Attacks that exploit this kind of access
Remove old task artifact directories by age, with dry-run support by default. It is categorised as a Destructive tool in the JS Reverse MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the JS Reverse MCP server in PolicyLayer and add a rule for prune_task_artifacts: 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 JS Reverse MCP. Nothing to install.
prune_task_artifacts 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_task_artifacts 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_task_artifacts. 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_task_artifacts is provided by the JS Reverse MCP server (noone-hub/jsreverser-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 →