AI agents call get_on_deck to retrieve information from Mcp Plex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user viewing history/watchlist data from Plex Media Server with no side effects. It queries existing data (the continue-watching list) without creating, modifying, deleting, or executing any operations. The read-only nature and minimal sensitivity of continue-watching metadata (compared to financial or destructive operations) make this a low-severity Read operation.
From the tool's definition Tool name is 'get_on_deck' and description states 'Get the "On Deck" continue-watching list from Plex' — uses 'Get' verb indicating retrieval without modification.
Attacks that exploit this kind of access
Get the "On Deck" continue-watching list from Plex. It is categorised as a Read tool in the Mcp Plex MCP Server, which means it retrieves data without modifying state.
Register the Mcp Plex MCP server in PolicyLayer and add a rule for get_on_deck: 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 Mcp Plex. Nothing to install.
get_on_deck 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_on_deck 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_on_deck. 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_on_deck is provided by the Mcp Plex MCP server (obrien-matthew/mcp-plex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_on_deck is one line of Mcp Plex's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →