Critical Risk →

pf_media_prune

Manually trigger a prune of remote media older than N days. The scheduled horizon job handles this on a recurring cadence; this lets operators force an aggressive pass. Rate-limited: 2/hour.

How to control pf_media_prune ↓

What pf_media_prune does on Crow

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

Critical Risk

Why pf_media_prune needs a policy

Pruning remote media permanently removes files that cannot be recovered. The description explicitly frames this as a forceful, aggressive deletion operation beyond normal scheduled cleanup. Misuse could result in large-scale irreversible data loss across the platform.

From the tool's definition 'prune of remote media older than N days' and 'force an aggressive pass' — pruning media is irreversible deletion of stored content

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

How to control pf_media_prune

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

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

pf_media_prune 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 Crow — 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.

Related tools and policies

Go deeper

Questions about pf_media_prune

What does the pf_media_prune tool do? +

Manually trigger a prune of remote media older than N days. The scheduled horizon job handles this on a recurring cadence; this lets operators force an aggressive pass. Rate-limited: 2/hour. It is categorised as a Destructive tool in the Crow 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 pf_media_prune? +

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

What risk level is pf_media_prune? +

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

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

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

pf_media_prune is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ 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.