AI agents call get_board to retrieve information from Tickr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool retrieves and displays a kanban board visualization by grouping tickets by status. It is purely informational—no data is created, modified, deleted, or executed. It falls squarely under the Read category with low severity since unauthorized access to a board view carries minimal risk compared to write, destructive, or financial operations.
From the tool's definition Tool name 'get_board' and description 'Get kanban board view for a project (tickets grouped by status columns)' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get kanban board view for a project (tickets grouped by status columns). It is categorised as a Read tool in the Tickr MCP Server, which means it retrieves data without modifying state.
get_board accepts 1 parameter: project. Required: project. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr MCP server in PolicyLayer and add a rule for get_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 Tickr. Nothing to install.
get_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_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_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_board is provided by the Tickr MCP server (@k-system/tickr-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 →