Uploads an attachment (image, document, etc.) to a Jira issue. EFFICIENT METHOD (recommended for large files): - fileUrl: Provide URL to remote file - MINIMAL tokens (~60 tokens) Example: Upload to Dropbox/S3/imgur first, then provide URL DIRECT METHOD (for small files): - content: Base64 encoded...
AI agents use jira_add_attachment to create or update resources in Mcp Jira Stdio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jira Stdio environment.
This is a Write operation because it creates and adds new data (file attachments) to existing Jira issues in a reversible manner. While attachments can typically be deleted, the primary action is creation/addition.
From the tool's definition Uploads an attachment to a Jira issue - the tool performs a create/add operation that modifies Jira issue data by attaching files. The description explicitly states it 'Uploads an attachment' and 'Returns attachment metadata', confirming it creates new data.
Attacks that exploit this kind of access
Uploads an attachment (image, document, etc.) to a Jira issue. EFFICIENT METHOD (recommended for large files): - fileUrl: Provide URL to remote file - MINIMAL tokens (~60 tokens) Example: Upload to Dropbox/S3/imgur first, then provide URL DIRECT METHOD (for small files): - content: Base64 encoded content - WARNING: HIGH token cost (~330,000 tokens for 1MB file) Only suitable for small files (< 500 KB) Returns attachment metadata including ID and download URL. To reference the image in a comment or description, use wiki markup: !filename.png! or !filename.png|thumbnail!. It is categorised as a Write tool in the Mcp Jira Stdio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_add_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 Mcp Jira Stdio. Nothing to install.
jira_add_attachment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the jira_add_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_add_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_add_attachment is provided by the Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →