Low Risk

browser_get_download_list

Get the list of downloaded files

How to control browser_get_download_list ↓

What browser_get_download_list does on Search

AI agents call browser_get_download_list to retrieve information from Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why browser_get_download_list needs a policy

This tool retrieves information about downloaded files in the browser without side effects. It does not modify, delete, or execute anything. It simply returns a list of files that have already been downloaded, making it a Read operation with low severity.

From the tool's definition Tool name 'browser_get_download_list' and description 'Get the list of downloaded files' indicate a read-only operation that retrieves/queries existing data without modification, deletion, or execution.

Documented attack patterns abuse exactly the kind of access browser_get_download_list gives an agent:

How to control browser_get_download_list

PolicyLayer is an MCP gateway — it sits between your AI agents and Search, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_get_download_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_get_download_list": {}
  }
}

browser_get_download_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Search — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_get_download_list

What does the browser_get_download_list tool do? +

Get the list of downloaded files. It is categorised as a Read tool in the Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_get_download_list? +

Register the Search MCP server in PolicyLayer and add a rule for browser_get_download_list: 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 Search. Nothing to install.

What risk level is browser_get_download_list? +

browser_get_download_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_get_download_list? +

Yes. Add a rate_limit block to the browser_get_download_list 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.

How do I block browser_get_download_list completely? +

Set action: deny in the PolicyLayer policy for browser_get_download_list. 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.

What MCP server provides browser_get_download_list? +

browser_get_download_list is provided by the Search MCP server (@agent-infra/mcp-server-search). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Search tool call.

Start from Search, 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.

36 Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.