AI agents call get_server_statistics to retrieve information from Plex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries existing bandwidth statistics from the Plex server. It does not create, modify, delete, execute code, trigger operations, or affect financial systems. The read-only nature is explicitly stated in the server description. Blast radius if misused is minimal — an agent could only learn about past data transfer patterns, which poses no security or operational risk.
From the tool's definition Tool description states 'Get Plex Media Server bandwidth statistics' — retrieves historical usage data with no modification capability.
Attacks that exploit this kind of access
Get Plex Media Server bandwidth statistics — total data transferred, broken down by LAN vs WAN, over a chosen time window. It is categorised as a Read tool in the Plex MCP Server, which means it retrieves data without modifying state.
Register the Plex MCP server in PolicyLayer and add a rule for get_server_statistics: 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 Plex. Nothing to install.
get_server_statistics 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 get_server_statistics 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 get_server_statistics. 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.
get_server_statistics is provided by the Plex MCP server (x10send/plex-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 →