get_issue

Get details of a specific issue

SERVERMcp Jira SOURCE1broseidon/mcp-jira-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/1broseidon-mcp-jira-server/get-issue.md

WHAT IT DOES

What get_issue does on Mcp Jira

AI agents call get_issue to retrieve information from Mcp Jira without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_issue is rated Low

This tool retrieves information about a Jira issue without creating, modifying, or deleting any data. It is a read-only operation that queries existing data, making it a Read category tool with low severity since the blast radius of misuse is limited to unauthorized information disclosure rather than data manipulation or destruction.

From the tool's definition Tool name 'get_issue' and description 'Get details of a specific issue' indicate data retrieval with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_issue safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Jira, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_issue, this is the rule to start with:

get_issue Allowed

get_issue is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_issue": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Jira, apply this rule, and every get_issue call is checked against it from then on.

FAQ

Questions about get_issue

What does the get_issue tool do? +

Get details of a specific issue. It is categorised as a Read tool in the Mcp Jira MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_issue? +

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

What risk level is get_issue? +

get_issue is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_issue? +

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

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

get_issue is provided by the Mcp Jira MCP server (1broseidon/mcp-jira-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Jira, and thousands of servers like it.

This server

All 6 Mcp Jira tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →