getJiraIssue

THE RISK

Low Risk

Why getJiraIssue needs a policy

This tool retrieves issue data from Jira by key lookup. It performs no side effects—no creation, modification, deletion, or code execution. The operation is purely informational and reversible. Classified as Read with low severity because unauthorized access to issue details could expose sensitive project information, but the blast radius is limited to information disclosure.

From the tool's definition Tool name 'getJiraIssue' and description 'Fetches a Jira issue by its key' indicate data retrieval without modification. The verb 'fetches' is characteristic of read-only operations.

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

POLICY

How to control getJiraIssue

PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Toolset, and nothing reaches the server without passing your rules. This is the rule we recommend for getJiraIssue:

policy.json

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

getJiraIssue is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Jira MCP Toolset — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jira MCP Toolset tools

Write issueCreation_createIssue Finalizes the wizard process by creating a Jira issue using the currently configured state Write issueCreation_initiateState Initialize a new, empty state for the issue creation wizard. Useful for testing state pers Write issueCreation_resetState Resets the issue creation wizard state completely, clearing any selected project, issue ty Write issueCreation_setAnalysisComplete Sets the analysis complete flag for the current issue creation session Write issueCreation_setUserConfirmation Sets the user confirmation flag for the current issue creation session. CRITICAL: Wait for Write issueCreation_updateFields Update and validate specific field values in the wizard state after retrieving the necessa Write issueCreation_updateState Update the core state of the issue creation wizard. Use this to set the Write issueUpdateWizard_updateIssueFromState Update a Jira issue using the current state. This tool works in two modes: 1) Immediately

All 19 Jira MCP Toolset tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getJiraIssue

What does the getJiraIssue tool do? +

Fetches a Jira issue by its key. It is categorised as a Read tool in the Jira MCP Toolset MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getJiraIssue? +

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

What risk level is getJiraIssue? +

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

Can I rate-limit getJiraIssue? +

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

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

getJiraIssue is provided by the Jira MCP Toolset MCP server (tbreeding/jira-mcp). 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 Toolset tool call.

Start from Jira MCP Toolset, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →