AI agents call jira_download_attachments to retrieve information from Jiraxmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/fetches attachments from a Jira issue and saves them locally. It is a read-only operation that does not modify, delete, or execute code. The blast radius is low: downloading attachments cannot corrupt data, trigger external operations, or cause financial harm. Confidence is high because the description clearly indicates a retrieval action.
From the tool's definition Tool name contains 'download' and description states 'Download all attachments for a Jira issue' — a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Download all attachments for a Jira issue into ~/.jiraxmcp/attachments/<issueKey>. It is categorised as a Read tool in the Jiraxmcp MCP Server, which means it retrieves data without modifying state.
Register the Jirax 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 Jiraxmcp. 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 Jirax MCP server (vaibhavpandeyvpz/jiraxmcp). 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 →