High Risk →

radarr_trigger_search

Trigger a search for missing movies, optionally for a specific movie

How to control radarr_trigger_search ↓

AI agents invoke radarr_trigger_search to trigger actions in Plex MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

radarr_trigger_search triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Plex MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for radarr_trigger_search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "radarr_trigger_search": {
      "limits": [
        {
          "counter": "radarr_trigger_search_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

radarr_trigger_search stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Plex 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the radarr_trigger_search tool do? +

Trigger a search for missing movies, optionally for a specific movie. It is categorised as a Execute tool in the Plex MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on radarr_trigger_search? +

Register the Plex MCP Server MCP server in PolicyLayer and add a rule for radarr_trigger_search: 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 Plex MCP Server. Nothing to install.

What risk level is radarr_trigger_search? +

radarr_trigger_search is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit radarr_trigger_search? +

Yes. Add a rate_limit block to the radarr_trigger_search 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 radarr_trigger_search completely? +

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

radarr_trigger_search is provided by the Plex MCP Server MCP server (niavasha/plex-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Plex MCP Server tool call.

Deterministic rules across all 54 Plex MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

54 Plex MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.