AI agents call get_task_statuses to retrieve information from Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves workflow metadata (valid status transitions) from Jira without creating, modifying, deleting, or executing any external operations. It has no side effects and poses minimal security risk, as it only exposes information about available task statuses that an AI agent would need to validate transitions before attempting updates.
From the tool's definition Tool description states 'Get available workflow transitions for a task' — a query operation that retrieves status information without modifying state.
Attacks that exploit this kind of access
Get available workflow transitions for a task. Call this before update_task_status to see valid target statuses. It is categorised as a Read tool in the Jira MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP server in PolicyLayer and add a rule for get_task_statuses: 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. Nothing to install.
get_task_statuses 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_task_statuses 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_task_statuses. 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_task_statuses is provided by the Jira MCP server (softspark/jira-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 →