Retrieves available statuses (global or project-specific, e.g., To Do, In Progress, Done). Returns status categories and workflow information.
AI agents call jira_get_statuses to retrieve information from Mcp Jira Stdio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectKey | string | — | Project key to get statuses for specific project |
issueTypeId | string | — | Issue type ID to get statuses for specific issue type |
Parameters from the server's own tool schema.
This tool queries Jira's status metadata without modifying, creating, deleting, or executing anything. It is purely informational—fetching enumerated workflow states. This is a safe read operation with minimal blast radius if misused.
From the tool's definition Tool name 'jira_get_statuses' and description state it 'Retrieves available statuses' and 'Returns status categories and workflow information.' The verb 'Retrieves' and 'Returns' indicate query/read operations with no side effects.
Attacks that exploit this kind of access
Retrieves available statuses (global or project-specific, e.g., To Do, In Progress, Done). Returns status categories and workflow information. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
jira_get_statuses accepts 2 parameters: projectKey, issueTypeId. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_get_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 Mcp Jira Stdio. Nothing to install.
jira_get_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 jira_get_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 jira_get_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.
jira_get_statuses is provided by the Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →