// SCAN REPORT

Mcp Jira Stdio

23 tools. 8 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 5 Jul 2026

8 can modify or destroy data

15 read-only

23 tools total

Verified server · catalogue entry verified 05/07/2026 · full schemas captured for 20 of 23 tools

How to control Mcp Jira Stdio ↓

TOOL MAP

What Mcp Jira Stdio exposes to your agents

Read (15) Write / Execute (7) Destructive / Financial (1)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Mcp Jira Stdio costs in tokens

3,991 tokens of tool definitions, loaded on every request

2.0% of a 200k context window

410 heaviest tool: jira_create_issue

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mcp Jira Stdio tools

Destructive · High jira_delete_attachment Deletion of attachments is an irreversible operation that cannot be undone—once removed, the attachment is gone. Write · Medium jira_add_attachment This is a Write operation because it creates and adds new data (file attachments) to existing Jira issues in a reversible manner. Write · Medium jira_add_comment Adding a comment is a write operation that creates new data in Jira reversibly (comments can be edited or deleted). Write · Medium jira_create_issue This tool creates new data in Jira (a reversible operation).

8 of Mcp Jira Stdio's 23 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mcp Jira Stdio

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Jira Stdio, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "jira_delete_attachment": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "jira_add_attachment": {
    "limits": [
      {
        "counter": "jira_add_attachment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "jira_get_attachments": {
    "limits": [
      {
        "counter": "jira_get_attachments_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Mcp Jira Stdio — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP JIRA STDIO →

Instant setup, no code required.

FULL CATALOGUE

All 23 Mcp Jira Stdio tools

DESTRUCTIVE 1 tools

Destructive jira_delete_attachment Deletes an attachment from Jira by its attachment ID. Use jira_get_attachments to find attachment IDs.

WRITE 7 tools

Write jira_add_attachment Uploads an attachment (image, document, etc.) to a Jira issue. EFFICIENT METHOD (recommended for large files) Write jira_add_comment Adds a comment to an issue. Supports visibility restrictions for groups or roles. Comment format is controlled Write jira_create_issue Creates a new Jira issue in the specified project. Supports setting issue type, priority, assignee, labels, co Write jira_create_issue_link Creates a link between two Jira issues. Supports common link types like "blocks", "relates", "duplicates", and Write jira_create_subtask Creates a subtask under an existing parent issue. Automatically determines the correct project and subtask iss Write jira_transition_issue Transitions a Jira issue to a new workflow status (e.g., "To Do" -> "In Progress" -> "Done"). Use jira_get_tra Write jira_update_issue Updates an existing Jira issue by its key. Supports updating summary, description, priority, assignee, labels,

READ 15 tools

Read jira_get_attachments Lists all attachments on a Jira issue. Returns attachment metadata including filename, size, MIME type, author Read jira_get_comments Retrieves all comments for a Jira issue. Returns comment author, content, timestamps, and visibility settings. Read jira_get_create_meta Retrieves create metadata for a project, showing all available fields (including custom fields) for creating i Read jira_get_custom_fields Retrieves all custom fields available in Jira. Shows custom field names, IDs (e.g., customfield_10071), and ty Read jira_get_issue Retrieve details for a specific Jira issue by key or URL. Use this when the user mentions an issue like "PAYWA Read jira_get_issue_graph Build a dependency/relationship graph starting from a seed issue. Returns a map of connected issues (parent/ch Read jira_get_issue_types Retrieves available issue types. Can get global issue types or project-specific issue types including regular Read jira_get_my_issues Retrieves issues assigned to current user, sorted by most recently updated first. Supports pagination and fiel Read jira_get_priorities Retrieves available priorities (e.g., Highest, High, Medium, Low, Lowest). Returns IDs, names, and description Read jira_get_project_info Retrieves detailed information about a project (components, versions, issue types, roles, insights). More comp Read jira_get_statuses Retrieves available statuses (global or project-specific, e.g., To Do, In Progress, Done). Returns status cate Read jira_get_transitions Retrieves all available workflow transitions for a Jira issue. Use this to discover which status changes are p Read jira_get_users Search for users by name, email, username, or account ID. Returns display name, email, account status, and acc Read jira_get_visible_projects Retrieves all projects accessible to the authenticated user. Returns project keys, names, descriptions, and ba Read jira_search_issues Search for Jira issues using JQL. Supports complex queries with pagination and field selection. Examples: "pro

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Mcp Jira Stdio

Can an AI agent delete data through the Mcp Jira Stdio MCP server? +

Yes. The Mcp Jira Stdio server exposes 1 destructive tools including jira_delete_attachment. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Mcp Jira Stdio? +

The Mcp Jira Stdio server has 7 write tools including jira_add_attachment, jira_add_comment, jira_create_issue. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mcp Jira Stdio.

How many tools does the Mcp Jira Stdio MCP server expose? +

23 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 8 can modify, create, or delete data.

How do I enforce a policy on Mcp Jira Stdio? +

Register the Mcp Jira Stdio MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Mcp Jira Stdio tool call.

Deterministic rules across all 23 Mcp Jira Stdio tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP JIRA STDIO →

Instant setup, no code required.

23 Mcp Jira Stdio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.