AI agents call get_watch_history 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 retrieves historical viewing data from a Plex server without modifying, deleting, or executing any operations. It is a pure read operation that returns informational records about what content was watched and when. Even if misused by an agent, it only exposes viewing history metadata with no capability to alter system state or trigger external actions.
From the tool's definition Tool name 'get_watch_history' and description 'Get playback history — what was watched, when, and how far' indicate data retrieval only.
Attacks that exploit this kind of access
Get playback history — what was watched, when, and how far. Use for. 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_watch_history: 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_watch_history 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_watch_history 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_watch_history. 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_watch_history 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 →