add_attachment_from_public_url

THE RISK

Medium Risk

Why add_attachment_from_public_url needs a policy

This tool creates a new attachment associated with a ticket, which is a reversible write operation. While attachments could potentially contain malicious content, the tool itself performs content addition rather than execution or deletion. Severity is medium because misuse could add unwanted or malicious attachments to tickets, but this is easily reversible by deletion.

From the tool's definition Tool adds an attachment to a Jira ticket via the API endpoint /rest/api/3/issue/{issueIdOrKey}/attachments. The action creates a new attachment resource, which is data modification.

Documented attack patterns abuse exactly the kind of access add_attachment_from_public_url gives an agent:

POLICY

How to control add_attachment_from_public_url

PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_attachment_from_public_url:

policy.json

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

add_attachment_from_public_url 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.

Create a free account and register Jira MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jira MCP Server tools

Destructive delete_ticket Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown i Execute execute_jql Execute a JQL query on Jira on the api /rest/api/3/search/jql. Do not use markdown in your Write add_attachment_from_confluence Add an attachment to a ticket on Jira from a Confluence page by its name on the api /rest/ Write assign_ticket Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use m Write create_ticket Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field. Write edit_ticket Edit a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in Read get_all_statuses Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your quer Read get_only_ticket_name_and_description Get the name and description of the requested tickets on the api /rest/api/3/search/jql. D

All 11 Jira MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about add_attachment_from_public_url

What does the add_attachment_from_public_url tool do? +

Add an attachment from a public url to a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/attachments. Do not use markdown in your query. 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 add_attachment_from_public_url? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for add_attachment_from_public_url: 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 add_attachment_from_public_url? +

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

Can I rate-limit add_attachment_from_public_url? +

Yes. Add a rate_limit block to the add_attachment_from_public_url 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 add_attachment_from_public_url completely? +

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

add_attachment_from_public_url is provided by the Jira MCP Server MCP server (ks-gen-ai/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Jira MCP Server tool call.

Start from Jira MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →