update_recording · Plex MCP: Risk & Policy

WHAT IT DOES

What update_recording does on Plex

AI agents use update_recording to create or update resources in Plex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plex environment.

WHY IT NEEDS A POLICY

Why update_recording needs a policy

The tool name 'update_recording' indicates modification of recording data. Although the server is advertised as read-only, this tool explicitly modifies state by updating a recording resource. This is a Write operation with high severity because unintended updates to Plex recordings (schedule changes, metadata alterations) could disrupt a user's media library and viewing plans.

From the tool's definition Tool name is 'update_recording'; server description states it is 'read-only against your local Plex instance', but this tool performs a write operation (update) on recordings, contradicting the read-only claim.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_recording Rate-limited

update_recording stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_recording": {
      "limits": [
        {
          "counter": "update_recording_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Plex, so you can run agents against it safely.

FAQ

Questions about update_recording

What does the update_recording tool do? +

update_recording. It is categorised as a Write tool in the Plex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_recording? +

Register the Plex MCP server in PolicyLayer and add a rule for update_recording: 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.

What risk level is update_recording? +

update_recording is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_recording? +

Yes. Add a rate_limit block to the update_recording 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.

How do I block update_recording completely? +

Set action: deny in the PolicyLayer policy for update_recording. 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.

What MCP server provides update_recording? +

update_recording 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.