Get available issue types for a Jira project
AI agents call get_issue_types to retrieve information from Sentry Investigator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely fetches and returns configuration data (issue types) from a Jira project. It does not create, modify, delete, or execute any actions. The operation is read-only and informational, making it a Read category risk with low severity. An AI agent misusing this tool would have minimal security impact—it only gains visibility into project structure.
From the tool's definition Tool name 'get_issue_types' and description 'Get available issue types for a Jira project' indicate a query operation that retrieves metadata about a Jira project with no side effects.
Attacks that exploit this kind of access
Get available issue types for a Jira project. It is categorised as a Read tool in the Sentry Investigator MCP Server, which means it retrieves data without modifying state.
Register the Sentry Investigator 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 Sentry Investigator. 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 Sentry Investigator MCP server (vibe-code-agent/sentry-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 →