jira_upload_attachment · JIRA MCP Server MCP: Risk & Policy

WHAT IT DOES

What jira_upload_attachment does on JIRA MCP Server

AI agents use jira_upload_attachment to create or update resources in JIRA MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JIRA MCP Server environment.

WHY IT NEEDS A POLICY

Why jira_upload_attachment needs a policy

Uploading attachments modifies project state by adding files to issues reversibly. While an attachment could theoretically be deleted later, the action itself creates new data. This is a Write operation. Severity is medium because an agent could upload sensitive files, malware, or excessively large files to disrupt operations, but the core impact is data creation rather than destruction or financial harm.

From the tool's definition Tool name includes 'upload' and description states 'Upload a file as an attachment to a JIRA issue.' This creates new data (attachments) in JIRA without deletion or irreversible modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_upload_attachment Rate-limited

jira_upload_attachment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_upload_attachment": {
      "limits": [
        {
          "counter": "jira_upload_attachment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches JIRA MCP Server, so you can run agents against it safely.

FAQ

Questions about jira_upload_attachment

What does the jira_upload_attachment tool do? +

Upload a file as an attachment to a JIRA issue. It is categorised as a Write tool in the JIRA MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on jira_upload_attachment? +

Register the JIRA MCP Server MCP server in PolicyLayer and add a rule for jira_upload_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 JIRA MCP Server. Nothing to install.

What risk level is jira_upload_attachment? +

jira_upload_attachment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit jira_upload_attachment? +

Yes. Add a rate_limit block to the jira_upload_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.

How do I block jira_upload_attachment completely? +

Set action: deny in the PolicyLayer policy for jira_upload_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.

What MCP server provides jira_upload_attachment? +

jira_upload_attachment is provided by the JIRA MCP Server MCP server (suppleaardvark/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.