Download an attachment from a Jira issue to a local file.
AI agents call download_attachment to retrieve information from Simple Jira MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing data (an attachment) from a Jira issue without altering, creating, deleting, or executing anything. It has no side effects on the Jira system or the attachment itself. The action is read-only and the potential blast radius of misuse is minimal—at worst, an AI agent might download attachments it shouldn't have access to, but no data is modified or destroyed.
From the tool's definition download_attachment downloads a file from Jira to local storage; the verb 'download' combined with 'attachment from a Jira issue' describes a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Download an attachment from a Jira issue to a local file. It is categorised as a Read tool in the Simple Jira MCP MCP Server, which means it retrieves data without modifying state.
Register the Simple Jira 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 Simple Jira MCP. 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 Simple Jira MCP server (timohaa/simple-jira-mcp). 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 →