Low Risk

download_media

Downloads files from URLs using saved browser sessions.

How to control download_media ↓

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

Low Risk

Even though download_media only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

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

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

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

download_media 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 Auth Fetch — 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.

Go deeper

What does the download_media tool do? +

Downloads files from URLs using saved browser sessions. It is categorised as a Read tool in the Auth Fetch MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on download_media? +

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

What risk level is download_media? +

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

Can I rate-limit download_media? +

Yes. Add a rate_limit block to the download_media 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 download_media completely? +

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

download_media is provided by the Auth Fetch MCP server (ymw0407/auth-fetch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Auth Fetch tool call.

Deterministic rules across all 4 Auth Fetch tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4 Auth Fetch tools catalogued and risk-classified — across an index of 42,500+ 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.