Get attachment information including download URL. Returns attachment metadata and content URL.
AI agents call jira_download_attachments 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.
The tool retrieves and returns attachment metadata and URLs without modifying, deleting, or executing any operations. While it provides access to downloadable content, the action itself is read-only retrieval. Severity is low because downloading attachments typically has minimal blast radius in Jira environments, though the actual content downloaded could pose risks depending on what files are present.
From the tool's definition Tool description states 'Get attachment information including download URL' and 'Returns attachment metadata and content URL' — purely retrieval operations with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access jira_download_attachments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_download_attachments:
{
"version": "1",
"default": "deny",
"tools": {
"jira_download_attachments": {}
}
}jira_download_attachments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get attachment information including download URL. Returns attachment metadata and content URL. 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_attachments: 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_attachments 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_attachments 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_attachments. 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_attachments is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.