AI agents invoke download_files to trigger actions in Browserless MCP Server. 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.
Downloading files is an active browser operation that fetches remote content and writes it to the local filesystem. It goes beyond a pure read (which would only retrieve data in-memory/return data) — it triggers external requests and persists data to disk. Given the anti-detection/scraping context of this server, misuse could result in downloading malicious or large volumes of content.
From the tool's definition Tool name 'download_files' and description 'Handle file downloads' — description is minimal/uninformative, but downloading files involves triggering external browser operations (navigating to URLs, initiating downloads, writing files to disk) with side…
Documented attack patterns abuse exactly the kind of access download_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browserless MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for download_files:
{
"version": "1",
"default": "deny",
"tools": {
"download_files": {
"limits": [
{
"counter": "download_files_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}download_files 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.
Handle file downloads. It is categorised as a Execute tool in the Browserless MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Browserless MCP Server MCP server in PolicyLayer and add a rule for download_files: 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 Browserless MCP Server. Nothing to install.
download_files 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_files 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_files. 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_files is provided by the Browserless MCP Server MCP server (lizzard-solutions/browserless-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browserless MCP Server, 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.
16 Browserless MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.