plex_refresh_library · Homelab MCP: Risk & Policy

WHAT IT DOES

What plex_refresh_library does on Homelab

AI agents invoke plex_refresh_library to trigger actions in Homelab. 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.

WHY IT NEEDS A POLICY

Why plex_refresh_library needs a policy

This tool executes an operation that initiates a background process in Plex rather than simply reading data. While not destructive or financial, it triggers a real-world action external to the AI system. The scan operation could consume significant resources on the homelab or affect media availability/visibility.

From the tool's definition Tool triggers a Plex library scan operation ('Trigger a Plex library scan'). This invokes an external process/service action whose effects depend on the media library state and contents.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

plex_refresh_library Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "plex_refresh_library": {
      "limits": [
        {
          "counter": "plex_refresh_library_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 plex_refresh_library

What does the plex_refresh_library tool do? +

Trigger a Plex library scan to pick up newly added files. It is categorised as a Execute tool in the Homelab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on plex_refresh_library? +

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

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

Can I rate-limit plex_refresh_library? +

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

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

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