radarr_manual_import · Homelab MCP: Risk & Policy

WHAT IT DOES

What radarr_manual_import does on Homelab

AI agents use radarr_manual_import to create or update resources in Homelab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Homelab environment.

WHY IT NEEDS A POLICY

Why radarr_manual_import needs a policy

The tool scans a local folder and imports video files into Radarr's library—a modification operation that adds or updates records in the system. This is a Write-class action as it creates new entries in Radarr's database/collection. Severity is medium because misuse could clutter or pollute the media library with unwanted content, but the action is reversible (imports can typically be removed).

From the tool's definition Tool description states it will 'import' video files into Radarr, which creates or modifies state in the media management system. The action is reversible (files can be removed from the collection), distinguishing it from destructive operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

radarr_manual_import Rate-limited

radarr_manual_import stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "radarr_manual_import": {
      "limits": [
        {
          "counter": "radarr_manual_import_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Homelab, so you can run agents against it safely.

FAQ

Questions about radarr_manual_import

What does the radarr_manual_import tool do? +

Scan a local folder for video files and import them into Radarr. It is categorised as a Write tool in the Homelab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on radarr_manual_import? +

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

What risk level is radarr_manual_import? +

radarr_manual_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit radarr_manual_import? +

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

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

radarr_manual_import is provided by the Homelab MCP server (nainounen/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.