Get a kanban-style board view for a sprint, grouping issues by status column. e.g., sprintId:
AI agents call get_sprint_board to retrieve information from Issue Tracker MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays sprint board information in a read-only manner. It queries existing data (issues grouped by status) without creating, modifying, deleting, or executing any operations. The verb 'get' and the passive nature of 'board view' confirm this is a Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_sprint_board' and description indicate retrieval of kanban board view data, grouping issues by status column. No modification, deletion, or execution of code/commands is performed.
Attacks that exploit this kind of access
Get a kanban-style board view for a sprint, grouping issues by status column. e.g., sprintId:. It is categorised as a Read tool in the Issue Tracker MCP MCP Server, which means it retrieves data without modifying state.
Register the Issue Tracker MCP server in PolicyLayer and add a rule for get_sprint_board: 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 Issue Tracker MCP. Nothing to install.
get_sprint_board 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_sprint_board 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_sprint_board. 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_sprint_board is provided by the Issue Tracker MCP server (josephtandle/jira-mcp-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 →