search_tickets_all
AI agents call search_tickets_all to retrieve information from Freshservice MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'search_' prefix and '_all' suffix are standard patterns for read operations that retrieve data. No modification, deletion, or execution of external operations is implied. Empty description lowers confidence slightly, but the naming convention and sibling tools (which show write/execute/destructive capabilities) strongly suggest this is a retrieval function.
From the tool's definition Tool name 'search_tickets_all' indicates retrieval of ticket data. Description is empty, but the name and context (Freshservice IT service management platform) suggest querying/listing tickets without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
search_tickets_all. It is categorised as a Read tool in the Freshservice MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for search_tickets_all: 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 Freshservice MCP Server. Nothing to install.
search_tickets_all 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_all 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_all. 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_all is provided by the Freshservice MCP Server MCP server (leemangold/freshservice_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 →