Request media with auto-confirm for TV ≤24 eps. Single/batch with validation.\n
AI agents use request_media to create or update resources in Overseerr MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Overseerr MCP Server environment.
This tool creates media requests (potentially in batch), which is a Write operation. It does not delete data or move money. The auto-confirm behavior for TV shows under 24 episodes means it can trigger approvals automatically, slightly elevating severity, but the blast radius is limited to queuing media downloads in a Plex ecosystem.
From the tool's definition 'Request media' — creates media requests in Overseerr; 'auto-confirm for TV ≤24 eps' and 'Single/batch with validation' indicate creation of new request records
Documented attack patterns abuse exactly the kind of access request_media gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Overseerr MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for request_media:
{
"version": "1",
"default": "deny",
"tools": {
"request_media": {
"limits": [
{
"counter": "request_media_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} request_media 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.
Free to start. No card required.
Request media with auto-confirm for TV ≤24 eps. Single/batch with validation.\n. It is categorised as a Write tool in the Overseerr MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Overseerr MCP Server MCP server in PolicyLayer and add a rule for request_media: 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 Overseerr MCP Server. Nothing to install.
request_media is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the request_media 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 request_media. 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.
request_media is provided by the Overseerr MCP Server MCP server (jhomen368/overseerr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Overseerr 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.
6 Overseerr MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.