Manage browser downloads (list, pause, resume, cancel)
AI agents use manage_downloads to create or update resources in Pydoll — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pydoll environment.
While 'list' is a read operation, the tool's core functionality includes state-modifying actions (pause, resume, cancel) that alter the lifecycle of downloads. These are reversible write operations rather than destructive ones, as downloads can be resumed or restarted.
From the tool's definition Tool description states 'Manage browser downloads (list, pause, resume, cancel)'. The 'pause', 'resume', and 'cancel' operations modify the state of ongoing downloads, which are write operations that change system state reversibly.
Documented attack patterns abuse exactly the kind of access manage_downloads gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pydoll, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_downloads:
{
"version": "1",
"default": "deny",
"tools": {
"manage_downloads": {
"limits": [
{
"counter": "manage_downloads_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_downloads 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.
Manage browser downloads (list, pause, resume, cancel). It is categorised as a Write tool in the Pydoll MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pydoll MCP server in PolicyLayer and add a rule for manage_downloads: 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 Pydoll. Nothing to install.
manage_downloads 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 manage_downloads 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 manage_downloads. 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.
manage_downloads is provided by the Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pydoll, 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.
57 Pydoll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.