AI agents call jira_download_attachment to retrieve information from Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reads an existing attachment without creating, modifying, deleting, or executing anything. It is a straightforward data retrieval operation that returns a file path to a temporary copy. The temporary file is not a side effect that affects system state beyond providing access to data. This clearly falls under the Read category.
From the tool's definition Tool description states it 'Downloads a Jira attachment by ID, saves it to a temp file, and returns the file path.' The operation is retrieval-only with no modification, deletion, or execution of the downloaded content.
Attacks that exploit this kind of access
Downloads a Jira attachment by ID, saves it to a temp file, and returns the file path. It is categorised as a Read tool in the Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Atlassian 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 Atlassian. 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 Atlassian MCP server (tingyiy/atlassian-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 →