PyLoad download manager. Three actions: - status: shows PyLoad queue AND lists folders in /downloads/ ready to organize - organize: moves downloaded files to Jellyfin library (runs async for archives). For movies use libraryFolder=
AI agents invoke download_status 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.
The 'status' action is a pure read, but the 'organize' action moves files between directories and triggers asynchronous processing. Since the tool spans categories, the most severe applicable category is Execute (file movement, async job triggering). Severity is high because misuse could misplace or incorrectly organize large amounts of media library content, potentially disrupting the Jellyfin library structure.
From the tool's definition 'organize: moves downloaded files to Jellyfin library (runs async for archives)' — triggers file movement operations and async execution based on arguments
Documented attack patterns abuse exactly the kind of access download_status 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 download_status:
{
"version": "1",
"default": "deny",
"tools": {
"download_status": {
"limits": [
{
"counter": "download_status_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}download_status 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.
PyLoad download manager. Three actions: - status: shows PyLoad queue AND lists folders in /downloads/ ready to organize - organize: moves downloaded files to Jellyfin library (runs async for archives). For movies use libraryFolder=. 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 download_status: 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.
download_status 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 download_status 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 download_status. 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.
download_status 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.