Manage requests: get/list/approve/decline/delete. Supports filters and batching.\n
AI agents call manage_media_requests to permanently remove resources in Overseerr MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly supports delete and decline operations on media requests, which are irreversible (a deleted request cannot be restored; a declined request changes state permanently). Following the most-severe-applicable rule, Destructive takes precedence over Write (approve/list) and Read (get/list).
From the tool's definition manage_media_requests: 'approve/decline/delete' — the delete and decline actions are potentially irreversible operations on media requests
Documented attack patterns abuse exactly the kind of access manage_media_requests 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 manage_media_requests:
{
"version": "1",
"default": "deny",
"hide": [
"manage_media_requests"
]
} manage_media_requests disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Manage requests: get/list/approve/decline/delete. Supports filters and batching.\n. It is categorised as a Destructive tool in the Overseerr MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Overseerr MCP Server MCP server in PolicyLayer and add a rule for manage_media_requests: 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.
manage_media_requests is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the manage_media_requests 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 manage_media_requests. 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.
manage_media_requests 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.