AI agents call overseerr_get_requests 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.
This tool retrieves existing media request data from Overseerr without creating, modifying, deleting, or executing any actions. It has no side effects and presents minimal security risk—an AI agent querying requests cannot cause harm beyond potentially accessing information it shouldn't see (which is an authorization concern, not a tool capability concern).
From the tool's definition Tool name 'overseerr_get_requests' and description 'Get all media requests' indicate data retrieval with no modification. The verb 'get' and the absence of any write, delete, or execution keywords confirm this is a read-only query operation.
Documented attack patterns abuse exactly the kind of access overseerr_get_requests gives an agent:
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 overseerr_get_requests:
{
"version": "1",
"default": "deny",
"tools": {
"overseerr_get_requests": {}
}
}overseerr_get_requests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all media requests. It is categorised as a Read tool in the Arr Suite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Arr Suite MCP Server MCP server in PolicyLayer and add a rule for overseerr_get_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 Arr Suite MCP Server. Nothing to install.
overseerr_get_requests is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the overseerr_get_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 overseerr_get_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.
overseerr_get_requests 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.
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.