Get all available issue types (Bug, Story, Task, Epic, etc.) for a specific project. Returns type names, IDs, descriptions, and workflow information. Required before creating issues to know valid issueType values.
AI agents call get_issue_types to retrieve information from Raalarcon Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_issue_types retrieves metadata about available issue types in a Jira project. It performs no modification, deletion, execution, or financial operation. It is informational only, making it a Read category tool with low severity since the blast radius of misuse is minimal—an agent could only retrieve harmless schema information.
From the tool's definition Tool description states it 'Get all available issue types' and 'Returns type names, IDs, descriptions, and workflow information.' This is a pure query operation with no side effects.
Attacks that exploit this kind of access
Get all available issue types (Bug, Story, Task, Epic, etc.) for a specific project. Returns type names, IDs, descriptions, and workflow information. Required before creating issues to know valid issueType values. It is categorised as a Read tool in the Raalarcon Jira MCP Server, which means it retrieves data without modifying state.
Register the Raalarcon Jira MCP server in PolicyLayer and add a rule for get_issue_types: 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 Raalarcon Jira. Nothing to install.
get_issue_types 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_types 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_types. 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_types is provided by the Raalarcon Jira MCP server (raalarcon-jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_issue_types is one line of Raalarcon Jira's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →