Download an attachment from a Jira issue. Text files (txt, md, json, log) are returned inline. CSV, XLS, XLSX, PDF are parsed by Python and returned as structured text. Images and other binary files are returned as base64.
AI agents call jira_download_attachment to retrieve information from Jira Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and transforms existing attachment data for consumption without altering, deleting, or executing any operations on the Jira instance or the attachment contents. The parsing of file formats and base64 encoding are read-phase transformations.
From the tool's definition Tool description states: 'Download an attachment from a Jira issue' with parsing and return operations only. No modification, deletion, or execution of downloaded content is performed by the tool itself.
Attacks that exploit this kind of access
Download an attachment from a Jira issue. Text files (txt, md, json, log) are returned inline. CSV, XLS, XLSX, PDF are parsed by Python and returned as structured text. Images and other binary files are returned as base64. It is categorised as a Read tool in the Jira Dev MCP Server, which means it retrieves data without modifying state.
Register the Jira Dev MCP server in PolicyLayer and add a rule for jira_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 Jira Dev. Nothing to install.
jira_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 jira_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 jira_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.
jira_download_attachment is provided by the Jira Dev MCP server (jira-dev-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 →