AI agents call get_scheduled_recordings 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 scheduling information from a local Plex DVR system. It has no side effects, makes no modifications, and performs no destructive or executable operations. The mention of 'Use subscription IDs with cancel_recording' indicates that cancel_recording is a separate tool; get_scheduled_recordings itself only reads. Blast radius is minimal as misuse would only expose local recording metadata.
From the tool's definition Tool name is 'get_scheduled_recordings' and description states 'List all DVR recording subscriptions' — a retrieval operation. Server description confirms 'read-only against your local Plex instance'.
Attacks that exploit this kind of access
List all DVR recording subscriptions grouped by type (one-shot episodes vs. series season passes) with IDs, channels, and air times. Use subscription IDs 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_scheduled_recordings: 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_scheduled_recordings 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_scheduled_recordings 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_scheduled_recordings. 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_scheduled_recordings 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 →