Download an attachment from JIRA to a local file path.
AI agents call jira_download_attachment to retrieve information from JIRA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves/downloads existing attachment data from JIRA without creating, modifying, or deleting anything. This is a Read operation. Severity is medium rather than low because downloads to local file paths could expose sensitive information if misused (e.g., downloading confidential documents, source code, or credentials stored as attachments), representing a moderate blast radius for an AI agent with…
From the tool's definition Tool name indicates 'Download an attachment' and description states 'Download an attachment from JIRA to a local file path.' This is fundamentally a retrieval operation with no modification of JIRA data.
Attacks that exploit this kind of access
Download an attachment from JIRA to a local file path. It is categorised as a Read tool in the JIRA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JIRA MCP Server 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 MCP Server. 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 MCP Server MCP server (suppleaardvark/jira-mcp-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 →