gts_media_prune
Manually trigger pruning of remote media older than N days. The scheduled cron (scripts/media-prune.sh) runs daily; this lets operators force an aggressive prune.
This record as markdown: /tools/kh0pper-crow/gts-media-prune.md
What gts_media_prune does on Crow
AI agents call gts_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.
Why gts_media_prune is rated Critical
Pruning media is an irreversible deletion operation. The description explicitly mentions 'aggressive prune' which implies bulk deletion of remote media files. Once pruned, this data cannot be recovered from the local system. The high severity reflects the potential for large-scale data loss if misconfigured (e.g., N=0 days).
From the tool's definition 'pruning of remote media older than N days' and 'force an aggressive prune' — media files are permanently deleted, not reversibly removed
Attacks that exploit this kind of access
The rule that runs gts_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 gts_media_prune, this is the rule to start with:
gts_media_prune 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 Crow, apply this rule, and every gts_media_prune call is checked against it from then on.
Questions about gts_media_prune
Manually trigger pruning of remote media older than N days. The scheduled cron (scripts/media-prune.sh) runs daily; this lets operators force an aggressive prune. 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.
Register the Crow MCP server in PolicyLayer and add a rule for gts_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.
gts_media_prune 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 gts_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 gts_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.
gts_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.
Across the catalogue