Fetch a Jira issue with normalized fields, description text, and comments.
AI agents call get_issue to retrieve information from Universal Mcp Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information from Jira without creating, modifying, deleting, or executing any operations. It is a straightforward query operation that reads existing issue data. The low severity reflects minimal blast radius—unauthorized access could expose issue details, but causes no direct damage to systems or data integrity.
From the tool's definition Tool name 'get_issue' and description 'Fetch a Jira issue' indicate data retrieval. The verb 'Fetch' and the explicit mention of retrieving 'normalized fields, description text, and comments' confirm read-only access with no side effects or modifications.
Attacks that exploit this kind of access
Fetch a Jira issue with normalized fields, description text, and comments. It is categorised as a Read tool in the Universal Mcp Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Universal Mcp Toolkit 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 Universal Mcp Toolkit. Nothing to install.
get_issue is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_issue is provided by the Universal Mcp Toolkit MCP server (markgatcha/universal-mcp-toolkit). 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 →