AI agents call test_connection to retrieve information from PlexMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a connection test and retrieves server metadata. It has no side effects, does not modify data, does not execute commands, and does not delete or move resources. It is a read-only diagnostic operation that simply queries the Plex server's current state and connectivity status. Even if misused by an AI agent, it can only retrieve information about the media server, with minimal security impact.
From the tool's definition Tool name 'test_connection' and description 'Test basic Plex connection and return server info' indicates a diagnostic query operation that retrieves and returns server information without modifying or executing changes.
Attacks that exploit this kind of access
Test basic Plex connection and return server info. It is categorised as a Read tool in the PlexMCP MCP Server, which means it retrieves data without modifying state.
Register the Plex MCP server in PolicyLayer and add a rule for test_connection: 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.
test_connection 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 test_connection 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 test_connection. 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.
test_connection 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 →