AI agents call plex_get_libraries to retrieve information from Nas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that lists/retrieves available libraries from a Plex media server. It has no side effects, does not modify data, and does not execute commands or trigger external operations. The blast radius of misuse is minimal—an AI agent listing libraries cannot cause harm beyond information disclosure of what content is available.
From the tool's definition Tool name 'plex_get_libraries' and description 'Liste toutes les bibliothèques Plex (Films, Séries, Musique, etc.)' [Lists all Plex libraries (Movies, TV Shows, Music, etc.)] indicate a retrieval operation that queries existing data without modification.
Attacks that exploit this kind of access
Liste toutes les bibliothèques Plex (Films, Séries, Musique, etc.). It is categorised as a Read tool in the Nas MCP Server, which means it retrieves data without modifying state.
Register the Nas MCP server in PolicyLayer and add a rule for plex_get_libraries: 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 Nas. Nothing to install.
plex_get_libraries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the plex_get_libraries 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 plex_get_libraries. 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.
plex_get_libraries is provided by the Nas MCP server (matthieurosset/nas-mcp-server). 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 →