jira_attachments

THE RISK

Critical Risk

Why jira_attachments needs a policy

The tool supports delete operations on attachments, which is irreversible. Per the rules, when a tool spans categories the most severe applies: Destructive > Write > Read. Deletion of attachments cannot be undone, making this Destructive. Severity is high because an AI agent could inadvertently or maliciously delete attachments from Jira issues, causing permanent data loss across projects.

From the tool's definition Manage Jira issue attachments: list, read, upload, or delete.

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

POLICY

How to control jira_attachments

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 jira_attachments:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "jira_attachments"
  ]
}

jira_attachments disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jira MCP Server tools

Write jira_links Manage Jira issue links: add, remove, list relationships between two issues. Use get_link_ Write jira_comments Get or add comments on a Jira issue. Write jira_issues Manage Jira issues. Use get_create_metadata action in jira_search first before creating is Write jira_workflow Manage issue status transitions. Use get_transitions first, then transition with the ID. Read jira_search Search and discover Jira resources: issues via JQL, projects, users, or field metadata.

All 6 Jira MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Jira MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about jira_attachments

What does the jira_attachments tool do? +

Manage Jira issue attachments: list, read, upload, or delete. It is categorised as a Destructive tool in the Jira MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on jira_attachments? +

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

What risk level is jira_attachments? +

jira_attachments is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit jira_attachments? +

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

How do I block jira_attachments completely? +

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

What MCP server provides jira_attachments? +

jira_attachments is provided by the Jira MCP Server MCP server (pdogra1299/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 →