Remove a location from a library.
AI agents call remove_library_location 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.
Removing a library location from Plex will irreversibly delete that location's association with the library, potentially making media at that location inaccessible and losing metadata/watch history tied to it. This is an irreversible operation that has significant side effects, placing it in the Destructive category.
From the tool's definition Tool name 'remove_library_location' and description 'Remove a location from a library' — the verb 'remove' indicates deletion of a library location configuration, which cannot be easily undone.
Attacks that exploit this kind of access
Remove a location from 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 remove_library_location: 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.
remove_library_location 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 remove_library_location 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 remove_library_location. 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.
remove_library_location 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 →