List all accessible JIRA boards. Returns board IDs, names, types (scrum/kanban), and project keys.
AI agents call jira_list_boards to retrieve information from JIRA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about JIRA boards (IDs, names, types, project keys) with no side effects. It is a pure read operation analogous to 'list' or 'get'. The low severity reflects minimal blast radius—an AI agent misusing this tool could only discover board information already accessible to the authenticated user, posing no risk to data integrity, financial systems, or system execution.
From the tool's definition Tool name 'jira_list_boards' and description 'List all accessible JIRA boards. Returns board IDs, names, types (scrum/kanban), and project keys.' indicate a query operation that retrieves and returns metadata about existing boards without modifying any data.
Attacks that exploit this kind of access
List all accessible JIRA boards. Returns board IDs, names, types (scrum/kanban), and project keys. It is categorised as a Read tool in the JIRA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JIRA MCP Server MCP server in PolicyLayer and add a rule for jira_list_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 JIRA MCP Server. Nothing to install.
jira_list_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 jira_list_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 jira_list_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.
jira_list_boards is provided by the JIRA MCP Server MCP server (suppleaardvark/jira-mcp-server). 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 →