search_tickets_tool
AI agents call search_tickets_tool to retrieve information from MCP Request-tracker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests a search/query function for retrieving ticket data. The absence of a description lowers confidence slightly, but the naming convention is consistent with other retrieval tools on this server (get_my_open_tickets_tool, get_new_tickets_tool, get_ticket_history_tool). Search operations are read-only with no side effects, placing this firmly in the Read category with low severity.
From the tool's definition Tool name 'search_tickets_tool' indicates a query operation. No destructive, write, execute, or financial capabilities are implied by the name.
Attacks that exploit this kind of access
search_tickets_tool. It is categorised as a Read tool in the MCP Request-tracker MCP Server, which means it retrieves data without modifying state.
Register the MCP Request-tracker MCP server in PolicyLayer and add a rule for search_tickets_tool: 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 MCP Request-tracker. Nothing to install.
search_tickets_tool 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_tool 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_tool. 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_tool is provided by the MCP Request-tracker MCP server (crunchtools/mcp-request-tracker). 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 →