Force Radarr to rescan movie folders or a specific movie for new files.
AI agents invoke movie_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 Radarr (a media management application) to rescan folders. It executes an action on an external system rather than simply reading data or writing/modifying records. While it doesn't delete data, it actively triggers a scanning process whose effects depend on arguments (specific movie or all folders).
From the tool's definition Force Radarr to rescan movie folders or a specific movie for new files
Documented attack patterns abuse exactly the kind of access movie_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 movie_rescan:
{
"version": "1",
"default": "deny",
"tools": {
"movie_rescan": {
"limits": [
{
"counter": "movie_rescan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}movie_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 Radarr to rescan movie folders or a specific movie 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 movie_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.
movie_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 movie_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 movie_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.
movie_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.