AI agents call infoset_search_tickets to retrieve information from Infoset without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries ticket data based on search criteria. It has no side effects—it does not create, modify, delete, or execute anything. It is a read-only retrieval operation, classified as Read with low severity since searching existing tickets poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name indicates search functionality ('search_tickets') and description states it 'Search[es] Infoset tickets by keyword and optional filters' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search Infoset tickets by keyword and optional filters. It is categorised as a Read tool in the Infoset MCP Server, which means it retrieves data without modifying state.
Register the Infoset MCP server in PolicyLayer and add a rule for infoset_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 Infoset. Nothing to install.
infoset_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 infoset_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 infoset_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.
infoset_search_tickets is provided by the Infoset MCP server (sudohakan/infoset-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 →