AI agents call search_tickets 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 |
|---|---|---|---|
query | string | Yes | Fulltext search query |
project | string | — | Limit to project slug |
Parameters from the server's own tool schema.
This tool performs a fulltext search operation, which is a read-only data retrieval function. It queries existing ticket data and returns results without creating, modifying, deleting, or executing operations. The blast radius is minimal as it only exposes information already accessible to the authenticated user within the project management system.
From the tool's definition Tool name 'search_tickets' and description 'Fulltext search in ticket titles and content' indicate a query operation that retrieves data without modification.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Fulltext search in ticket titles and content. It is categorised as a Read tool in the Tickr MCP Server, which means it retrieves data without modifying state.
search_tickets accepts 2 parameters: query, project. Required: query. 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 search_tickets: 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.
search_tickets 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 search_tickets 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 search_tickets. 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.
search_tickets 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 →