AI agents call ticket_search to retrieve information from Tpm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'ticket_search' clearly denotes a retrieval operation typical of Read category tools. While the description is empty (reducing confidence slightly), the naming convention and the broader context of a project management tracking system where search is a standard read-only operation support classification as Read with low severity. No data modification, deletion, or external execution is implied.
From the tool's definition Tool name 'ticket_search' indicates a search/query operation. The server context is a project management system using SQLite for tracking projects, features, and tasks. Search operations retrieve data without modifying it.
Attacks that exploit this kind of access
ticket_search. It is categorised as a Read tool in the Tpm MCP Server, which means it retrieves data without modifying state.
Register the Tpm MCP server in PolicyLayer and add a rule for ticket_search: 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 Tpm. Nothing to install.
ticket_search 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 ticket_search 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 ticket_search. 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.
ticket_search is provided by the Tpm MCP server (urjitbhatia/tpm-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 →