Low Risk

plex_get_on_deck

Get On Deck (in progress) media

How to control plex_get_on_deck ↓

What plex_get_on_deck does on Arr Suite MCP Server

AI agents call plex_get_on_deck to retrieve information from Arr Suite MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why plex_get_on_deck needs a policy

This tool retrieves or queries data about media that is currently being watched or in progress ('On Deck' is a Plex feature showing in-progress content). It has no side effects—it only reads and returns information without modifying, deleting, or executing external operations.

From the tool's definition Tool name 'plex_get_on_deck' and description 'Get On Deck (in progress) media' indicate retrieval of status information about in-progress media content from Plex.

Documented attack patterns abuse exactly the kind of access plex_get_on_deck gives an agent:

How to control plex_get_on_deck

PolicyLayer is an MCP gateway — it sits between your AI agents and Arr Suite MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for plex_get_on_deck:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "plex_get_on_deck": {}
  }
}

plex_get_on_deck is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Arr Suite MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about plex_get_on_deck

What does the plex_get_on_deck tool do? +

Get On Deck (in progress) media. It is categorised as a Read tool in the Arr Suite MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on plex_get_on_deck? +

Register the Arr Suite MCP Server MCP server in PolicyLayer and add a rule for plex_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 Arr Suite MCP Server. Nothing to install.

What risk level is plex_get_on_deck? +

plex_get_on_deck is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit plex_get_on_deck? +

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

How do I block plex_get_on_deck completely? +

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

What MCP server provides plex_get_on_deck? +

plex_get_on_deck is provided by the Arr Suite MCP Server MCP server (shaktech786/arr-suite-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Arr Suite MCP Server tool call.

Start from Arr Suite MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

25 Arr Suite MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.