Get a direct download URL for a file. Works with any file type including videos.
AI agents call download_file to retrieve information from MCP Document Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Categorized as Read because the core function is retrieving/generating access to file data. However, severity is elevated to medium rather than low due to: (1) potential path traversal risks despite stated protections, (2) ability to access 'any file type' which could include sensitive non-document files outside the intended scope, and (3) the tool's direct download capability could expose files the AI agent should…
From the tool's definition Tool name is 'download_file' and description states 'Get a direct download URL for a file.' This is fundamentally a retrieval operation that generates a URL without modifying or executing operations.
Attacks that exploit this kind of access
Get a direct download URL for a file. Works with any file type including videos. It is categorised as a Read tool in the MCP Document Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Document Server MCP server in PolicyLayer and add a rule for download_file: 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 MCP Document Server. Nothing to install.
download_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the download_file 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_file. 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_file is provided by the MCP Document Server MCP server (watsona4/mcp-document-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →