Empty the trash for a library.
AI agents call empty_trash to permanently remove resources in PlexMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Emptying trash is an irreversible operation that permanently removes media items from the library. Once trash is emptied, the deleted content cannot be recovered through Plex. This qualifies as Destructive with high severity given the potential blast radius of permanently losing an entire library's worth of deleted media.
From the tool's definition 'Empty the trash for a library' — emptying trash permanently deletes items that have been marked for removal, which is irreversible.
Attacks that exploit this kind of access
Empty the trash for a library. It is categorised as a Destructive tool in the PlexMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Plex MCP server in PolicyLayer and add a rule for empty_trash: 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 PlexMCP. Nothing to install.
empty_trash 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 empty_trash 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 empty_trash. 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.
empty_trash is provided by the Plex MCP server (sandraschi/plexmcp). 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 →