AI agents call plex_get_watch_history to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries viewing data from Plex without creating, modifying, or deleting any information. It is a passive read operation with no side effects. Severity is low because the data returned (watch history metadata) is not sensitive enough to warrant higher risk in a homelab context, and misuse would only expose user viewing patterns without enabling destructive or financial actions.
From the tool's definition Tool name indicates 'get' operation; description states 'Show recent Plex watch history' with no modifications, deletions, or external state changes mentioned.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Show recent Plex watch history across all users with titles, types, and play counts. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for plex_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 Homelab. Nothing to install.
plex_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 plex_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 plex_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.
plex_get_watch_history is provided by the Homelab MCP server (nainounen/homelab-mcp). 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 →