Get list of available Jira boards for ticket creation
AI agents call get_jira_boards 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 retrieves metadata about available Jira boards to inform downstream operations. It performs a read-only query with no ability to modify, delete, or execute actions. The blast radius of misuse is minimal—an agent could at most learn what boards exist, which is low-sensitivity information. Severity is low because board lists are typically non-sensitive administrative data.
From the tool's definition Tool name 'get_jira_boards' and description 'Get list of available Jira boards for ticket creation' indicate a simple query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Get list of available Jira boards for ticket creation. 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_jira_boards: 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_jira_boards 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_jira_boards 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_jira_boards. 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_jira_boards 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 →