Identify duplicate DVR recording subscriptions — same show or GUID scheduled more than once. Groups by guid (primary) or title (fallback), returning duplicate groups with IDs so you can cancel the extras with cancel_recording.
AI agents call get_recording_conflicts 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 performs a query/search operation that retrieves and groups recording metadata. It has no side effects — it does not modify, delete, or execute any actions. The severity is low because misuse would only expose scheduling information about the user's DVR, with no blast radius for unintended data loss or external actions.
From the tool's definition Tool description explicitly states it 'Identify[s] duplicate DVR recording subscriptions' and 'returning duplicate groups with IDs' — it queries and retrieves information about existing recordings.
Attacks that exploit this kind of access
Identify duplicate DVR recording subscriptions — same show or GUID scheduled more than once. Groups by guid (primary) or title (fallback), returning duplicate groups with IDs so you can cancel the extras with cancel_recording. 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_recording_conflicts: 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_recording_conflicts 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_recording_conflicts 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_recording_conflicts. 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_recording_conflicts 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 →