pt_media_prune
Trigger pruning of remote-cached video files older than N days. PeerTube runs this on a scheduled job; this forces an immediate pass. Admin-only. Rate-limited: 2/hour.
This record as markdown: /tools/kh0pper-crow/pt-media-prune.md
What pt_media_prune does on Crow
AI agents invoke pt_media_prune to trigger actions in Crow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why pt_media_prune is rated High
This tool executes a maintenance operation (pruning) that removes cached data from storage. While it targets data older than N days (suggesting intentional cleanup), it permanently deletes files from the remote cache, making it irreversible. However, it is scoped to deletion of aged, cached content rather than arbitrary data deletion, and its admin-only restriction with rate-limiting (2/hour) mitigates risk.
From the tool's definition Tool description states "Trigger pruning of remote-cached video files older than N days" and explicitly notes "Admin-only" access control.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs pt_media_prune safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pt_media_prune, this is the rule to start with:
pt_media_prune stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every pt_media_prune call is checked against it from then on.
Questions about pt_media_prune
Trigger pruning of remote-cached video files older than N days. PeerTube runs this on a scheduled job; this forces an immediate pass. Admin-only. Rate-limited: 2/hour. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for pt_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.
pt_media_prune is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pt_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.
Set action: deny in the PolicyLayer policy for pt_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.
pt_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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue