Get quality profiles, root folders, tags, and language profiles (Sonarr) for a Radarr/Sonarr server.
AI agents call get_service_details to retrieve information from Overseerr MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs information retrieval only, querying existing server configuration without side effects. Even though it accesses service details, this is informational metadata about system settings rather than affecting media content or operations. It falls cleanly into the Read category with low severity since it cannot modify state or cause damage.
From the tool's definition Tool retrieves configuration data: 'Get quality profiles, root folders, tags, and language profiles' from Radarr/Sonarr servers. These are read-only queries with no data modification, creation, or deletion capability.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_service_details 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 get_service_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_service_details": {}
}
}get_service_details 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 quality profiles, root folders, tags, and language profiles (Sonarr) for a Radarr/Sonarr server. It is categorised as a Read tool in the Overseerr MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Overseerr MCP Server MCP server in PolicyLayer and add a rule for get_service_details: 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.
get_service_details 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 get_service_details 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 get_service_details. 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.
get_service_details 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.