AI agents call overseerr_get_person to retrieve information from Nas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about people and their filmography from the Overseerr media server management system. It performs a read-only operation that retrieves existing data without modifying, deleting, or executing any actions. The low severity reflects minimal risk even if misused—an agent could only access information that is already publicly available through the media server.
From the tool's definition Tool name 'overseerr_get_person' and description 'Récupère les détails d'une personne (acteur, réalisateur) et sa filmographie' (Retrieves details of a person (actor, director) and their filmography) indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Récupère les détails d'une personne (acteur, réalisateur) et sa filmographie. It is categorised as a Read tool in the Nas MCP Server, which means it retrieves data without modifying state.
Register the Nas MCP server in PolicyLayer and add a rule for overseerr_get_person: 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 Nas. Nothing to install.
overseerr_get_person 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_person 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_person. 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_person is provided by the Nas MCP server (matthieurosset/nas-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 →