Fetch a Jira issue by key.
AI agents call jira_get_issue to retrieve information from Work Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing issue data from Jira by a specific key identifier. It does not create, modify, delete, execute code, or trigger external operations. The action is read-only and informational in nature, making it a Read category tool with low severity impact.
From the tool's definition Tool name 'jira_get_issue' and description 'Fetch a Jira issue by key' indicate retrieval of data without modification. The verb 'Fetch' is a query operation with no side effects.
Attacks that exploit this kind of access
Fetch a Jira issue by key. It is categorised as a Read tool in the Work Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Work Integrations 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 Work Integrations MCP. Nothing to install.
jira_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 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.
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.
jira_get_issue is provided by the Work Integrations MCP server (nazarky/workspace-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 →