lemmy_media_prune
Trigger a pict-rs prune of remote media. Exposes the admin purge endpoint; deletes cached media for federated posts older than N days. Rate-limited: 2/hour.
This record as markdown: /tools/kh0pper-crow/lemmy-media-prune.md
What lemmy_media_prune does on Crow
AI agents call lemmy_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 lemmy_media_prune is rated Critical
This tool irreversibly deletes data (cached media) without possibility of restoration. While the deletion targets older federated media rather than primary user data, it permanently removes content from the system. The rate-limiting (2/hour) suggests it is a privileged admin operation.
From the tool's definition Tool description explicitly states it "deletes cached media for federated posts older than N days" and "Exposes the admin purge endpoint". The term "purge" combined with "deletes" indicates irreversible data removal.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs lemmy_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 lemmy_media_prune, this is the rule to start with:
lemmy_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 lemmy_media_prune call is checked against it from then on.
Questions about lemmy_media_prune
Trigger a pict-rs prune of remote media. Exposes the admin purge endpoint; deletes cached media for federated posts older than N days. 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.
Register the Crow MCP server in PolicyLayer and add a rule for lemmy_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.
lemmy_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 lemmy_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 lemmy_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.
lemmy_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