Full investigation and fix workflow for a Jira issue. Accepts an issue key (AT-123) or full browse URL. Reads the issue, prior comments, linked issues, and attachments; detects duplicate analysis (idempotency); selects a type-aware template (Bug/Story/Task); and provides step-by-step SOP: explore...
AI agents invoke jira_analyze_task to trigger actions in Jira Dev. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool orchestrates a multi-step end-to-end workflow that goes beyond reading data: it implements fixes, runs builds/tests, and posts comments. The 'implement' and 'build verify' steps indicate it executes code changes and external operations. It also writes back to Jira (post analysis comment). Since it spans Execute and Write, Execute is the more severe category that applies.
From the tool's definition Full investigation and fix workflow... explore code → plan → baseline test → implement → build verify → post analysis comment. Use this instead of jira_read_task when you want to drive the full workflow end-to-end.
Attacks that exploit this kind of access
Full investigation and fix workflow for a Jira issue. Accepts an issue key (AT-123) or full browse URL. Reads the issue, prior comments, linked issues, and attachments; detects duplicate analysis (idempotency); selects a type-aware template (Bug/Story/Task); and provides step-by-step SOP: explore code → plan → baseline test → implement → build verify → post analysis comment. Use this instead of jira_read_task when you want to drive the full workflow end-to-end. It is categorised as a Execute tool in the Jira Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jira Dev MCP server in PolicyLayer and add a rule for jira_analyze_task: 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 Dev. Nothing to install.
jira_analyze_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the jira_analyze_task 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_analyze_task. 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_analyze_task is provided by the Jira Dev MCP server (jira-dev-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 →