Retrieve full details for a single issue including all comments. e.g., id:
AI agents call get_issue to retrieve information from Issue Tracker MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries data from an issue tracker without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that returns issue metadata and comment history. Blast radius is minimal since retrieval cannot alter system state or cause harm unless the returned data itself is sensitive, but the tool's function is inherently safe.
From the tool's definition Tool description states 'Retrieve full details for a single issue including all comments' — a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieve full details for a single issue including all comments. e.g., id:. It is categorised as a Read tool in the Issue Tracker MCP MCP Server, which means it retrieves data without modifying state.
Register the Issue Tracker 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 Issue Tracker MCP. 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 Issue Tracker MCP server (josephtandle/jira-mcp-mcp). 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 →