search_tickets
AI agents call search_tickets to retrieve information from RT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The server is explicitly read-only, and search_tickets performs a search operation typical of Read category tools. No description provided for the specific tool, but the server-level context and sibling tools (all retrieval-focused: get_attachment, get_ticket, get_ticket_correspondence, get_ticket_hierarchy) confirm this is a query/search function with no data modification or destructive capabilities.
From the tool's definition Server described as 'Read-only MCP server' enabling 'ticket search, retrieval, correspondence viewing, attachment download, and hierarchy exploration.' Tool name 'search_tickets' aligns with search capability (no side effects).
Attacks that exploit this kind of access
search_tickets. It is categorised as a Read tool in the RT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RT MCP Server 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 RT MCP Server. 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 RT MCP Server MCP server (msekoranja/rt-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 →