download_content_attachments
AI agents call download_content_attachments to retrieve information from MCP Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Downloading attachments is a read-only operation that retrieves existing data from Jira/Confluence without side effects. No creation, modification, deletion, or execution occurs. The severity is low because attachment downloads typically expose only files already accessible to the authenticated user, and misuse would result in information disclosure rather than system compromise.
From the tool's definition Tool name 'download_attachment' (and sibling 'download_attachments') indicates retrieval of attachment content. The description is empty, but the function name strongly suggests a read operation that retrieves stored files without modification or deletion.
Attacks that exploit this kind of access
download_content_attachments. It is categorised as a Read tool in the MCP Atlassian MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian MCP server in PolicyLayer and add a rule for download_content_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 MCP Atlassian. Nothing to install.
download_content_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 download_content_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 download_content_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.
download_content_attachments is provided by the MCP Atlassian MCP server (lklkxcxc/mcp-atlassian). 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 →