Low Risk

get_services

List configured Radarr/Sonarr servers. Returns ID, name, isDefault, 4K status, active defaults (directory, profile, tags).

How to control get_services ↓

What get_services does on Overseerr MCP Server

AI agents call get_services 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.

Low Risk

Why get_services needs a policy

This tool queries and returns existing configuration data about media server instances without creating, modifying, deleting, or executing any operations. It is a straightforward read-only operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_services' and description 'List configured Radarr/Sonarr servers' indicates retrieval of configuration metadata with no modification capability. Returns informational fields (ID, name, isDefault, 4K status, directory, profile, tags).

Documented attack patterns abuse exactly the kind of access get_services gives an agent:

How to control get_services

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_services:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_services": {}
  }
}

get_services is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Overseerr MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_services

What does the get_services tool do? +

List configured Radarr/Sonarr servers. Returns ID, name, isDefault, 4K status, active defaults (directory, profile, tags). It is categorised as a Read tool in the Overseerr MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_services? +

Register the Overseerr MCP Server MCP server in PolicyLayer and add a rule for get_services: 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.

What risk level is get_services? +

get_services is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_services? +

Yes. Add a rate_limit block to the get_services 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.

How do I block get_services completely? +

Set action: deny in the PolicyLayer policy for get_services. 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.

What MCP server provides get_services? +

get_services 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.

Enforce policy on every Overseerr MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.