Add URLs to PyLoad for downloading from file hosters (Mega, MediaFire, etc.). Use a descriptive packageName — it becomes the subfolder in downloads.
AI agents use download_add to create or update resources in Mediabox MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mediabox MCP environment.
This tool initiates new download jobs by adding URLs to PyLoad. It creates new entries/packages in the download manager, which is a Write operation. It does not execute arbitrary code, delete data, or involve financial transactions. Misuse could lead to downloading unwanted or malicious content, hence medium severity.
From the tool's definition Add URLs to PyLoad for downloading from file hosters (Mega, MediaFire, etc.)
Documented attack patterns abuse exactly the kind of access download_add 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_add:
{
"version": "1",
"default": "deny",
"tools": {
"download_add": {
"limits": [
{
"counter": "download_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}download_add 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.
Free to start. No card required.
Add URLs to PyLoad for downloading from file hosters (Mega, MediaFire, etc.). Use a descriptive packageName — it becomes the subfolder in downloads. It is categorised as a Write tool in the Mediabox MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mediabox MCP server in PolicyLayer and add a rule for download_add: 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_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the download_add 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_add. 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_add 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.