Deletes an attachment from Jira by its attachment ID. Use jira_get_attachments to find attachment IDs.
AI agents call jira_delete_attachment to permanently remove resources in Mcp Jira Stdio — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
attachmentId | string | Yes | ID of the attachment to delete |
Parameters from the server's own tool schema.
Deletion of attachments is an irreversible operation that cannot be undone—once removed, the attachment is gone. This clearly falls under the Destructive category. Severity is high because unauthorized deletion of project attachments could disrupt team collaboration and lose important documents, though the blast radius is limited to individual attachments rather than entire issues or projects.
From the tool's definition Tool name is 'jira_delete_attachment' and description states it 'Deletes an attachment from Jira by its attachment ID'. The verb 'Deletes' indicates irreversible removal of data.
Attacks that exploit this kind of access
Deletes an attachment from Jira by its attachment ID. Use jira_get_attachments to find attachment IDs. It is categorised as a Destructive tool in the Mcp Jira Stdio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
jira_delete_attachment accepts 1 parameter: attachmentId. Required: attachmentId. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_delete_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_delete_attachment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the jira_delete_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_delete_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_delete_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 →