radarr_set_path_mapping · Homelab MCP: Risk & Policy

WHAT IT DOES

What radarr_set_path_mapping does on Homelab

AI agents use radarr_set_path_mapping 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_set_path_mapping needs a policy

This tool modifies Radarr settings by creating or updating path mappings, which is a reversible Write operation. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial transactions. Path mapping misconfiguration could disrupt media management workflows or expose unintended directories, warranting medium severity.

From the tool's definition Tool description states 'Add or update a remote path mapping in Radarr,' indicating it creates or modifies configuration data in the Radarr media management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

radarr_set_path_mapping Rate-limited

radarr_set_path_mapping 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_set_path_mapping": {
      "limits": [
        {
          "counter": "radarr_set_path_mapping_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_set_path_mapping

What does the radarr_set_path_mapping tool do? +

Add or update a remote path mapping in 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_set_path_mapping? +

Register the Homelab MCP server in PolicyLayer and add a rule for radarr_set_path_mapping: 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_set_path_mapping? +

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

Can I rate-limit radarr_set_path_mapping? +

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

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

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