Force Sonarr to rescan a series folder for new files.
AI agents invoke series_rescan to trigger actions in Mediabox MCP. 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.
This tool triggers an external operation in Sonarr (a TV series management application) to rescan a folder. It executes an action on an external system rather than simply reading data or writing/modifying stored records. While it doesn't delete data, it initiates a process whose effects (file detection, metadata updates, library changes) depend on the current state of the filesystem and Sonarr's configuration.
From the tool's definition Force Sonarr to rescan a series folder for new files
Documented attack patterns abuse exactly the kind of access series_rescan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mediabox MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for series_rescan:
{
"version": "1",
"default": "deny",
"tools": {
"series_rescan": {
"limits": [
{
"counter": "series_rescan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}series_rescan 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.
Free to start. No card required.
Force Sonarr to rescan a series folder for new files. It is categorised as a Execute tool in the Mediabox MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mediabox MCP server in PolicyLayer and add a rule for series_rescan: 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 Mediabox MCP. Nothing to install.
series_rescan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the series_rescan 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.
Set action: deny in the PolicyLayer policy for series_rescan. 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.
series_rescan is provided by the Mediabox MCP server (juancmpdev/mediabox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mediabox MCP, 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.
30 Mediabox MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.