Delete a playlist.
AI agents call delete_playlist 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.
This tool permanently removes a playlist from the Plex Media Server. Deletion is an irreversible action that cannot be undone—the playlist and its contents are lost. This fits the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' While the blast radius is limited to a single playlist rather than the entire library,…
From the tool's definition Tool name is 'delete_playlist' with description 'Delete a playlist.' The verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a playlist. 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 delete_playlist: 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.
delete_playlist 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 delete_playlist 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 delete_playlist. 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.
delete_playlist 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 →