AI agents use overseerr_request_tv_to_library to create or update resources in Overseerr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Overseerr environment.
The tool appears to submit a request for a TV show to be added to the media library, which is a reversible write/create operation (requests can typically be deleted). The description is dynamic/unavailable, so confidence is reduced, but the naming pattern and server context strongly imply a Write action similar to the movie request sibling tool.
From the tool's definition Tool name 'overseerr_request_tv_to_library' suggests creating a new media request for a TV show to be added to a library, analogous to sibling tool 'overseerr_request_movie_to_library'
Attacks that exploit this kind of access
(Description is provided dynamically to the decorator). It is categorised as a Write tool in the Overseerr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Overseerr MCP server in PolicyLayer and add a rule for overseerr_request_tv_to_library: 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. Nothing to install.
overseerr_request_tv_to_library 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 overseerr_request_tv_to_library 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_request_tv_to_library. 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_request_tv_to_library is provided by the Overseerr MCP server (ptbsare/overseerr-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →