Low Risk

crow_plex_on_deck

Get the On Deck list — items ready to continue watching or recently added unwatched items

How to control crow_plex_on_deck ↓

What crow_plex_on_deck does on Crow

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

Low Risk

Why crow_plex_on_deck needs a policy

This tool queries data from a Plex media server to retrieve a viewing list. It performs a simple data retrieval operation with no capability to create, modify, delete, or execute actions. The only information exposed is media metadata about items on a user's watchlist, which presents minimal security risk.

From the tool's definition Tool retrieves 'On Deck list — items ready to continue watching or recently added unwatched items'. The verb 'Get' and the read-only nature of querying a viewing list with no modification or side effects.

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

How to control crow_plex_on_deck

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

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

crow_plex_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 Crow — 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 crow_plex_on_deck

What does the crow_plex_on_deck tool do? +

Get the On Deck list — items ready to continue watching or recently added unwatched items. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crow_plex_on_deck? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_plex_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 Crow. Nothing to install.

What risk level is crow_plex_on_deck? +

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

Can I rate-limit crow_plex_on_deck? +

Yes. Add a rate_limit block to the crow_plex_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 crow_plex_on_deck completely? +

Set action: deny in the PolicyLayer policy for crow_plex_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 crow_plex_on_deck? +

crow_plex_on_deck is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

Start from Crow, 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.

576 Crow 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.