download_attachment
Download email attachment to configured download path
This record as markdown: /tools/cowork-bench/download-attachment.md
What download_attachment does on Cowork Bench
AI agents call download_attachment to retrieve information from Cowork Bench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why download_attachment is rated Low
Downloading an attachment is a retrieval operation with no side effects on the source data. The attachment is copied to a local path but the original remains intact. This is a Read operation. Severity is low because attachment downloads are typically expected functionality with limited blast radius - the worst case is accessing unintended file contents.
From the tool's definition Tool description states 'Download email attachment to configured download path' - this retrieves/extracts an email attachment without modifying or deleting it.
Attacks that exploit this kind of access
The rule that runs download_attachment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For download_attachment, this is the rule to start with:
download_attachment is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every download_attachment call is checked against it from then on.
Questions about download_attachment
Download email attachment to configured download path. It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for download_attachment: 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 Cowork Bench. Nothing to install.
download_attachment 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_attachment 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_attachment. 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_attachment is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
This server
Across the catalogue