jira_get_issue

Get a Jira issue by key or ID

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/jira-get-issue.md

WHAT IT DOES

What jira_get_issue does on ScopeGate

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

RISK

Why jira_get_issue is rated Low

This tool retrieves/queries data from Jira without creating, modifying, or deleting any records. The verb 'Get' and the retrieval pattern are characteristic of Read category tools. The blast radius is low since viewing issue data poses minimal risk unless the content itself is sensitive, but the tool operation itself is non-destructive and non-executable.

From the tool's definition Tool name 'jira_get_issue' and description 'Get a Jira issue by key or ID' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jira_get_issue safely

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

jira_get_issue Allowed

jira_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": {
    "jira_get_issue": {}
  }
}

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

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

FAQ

Questions about jira_get_issue

What does the jira_get_issue tool do? +

Get a Jira issue by key or ID. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jira_get_issue? +

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

What risk level is jira_get_issue? +

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

Can I rate-limit jira_get_issue? +

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

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

jira_get_issue is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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