get_ticket_stats
AI agents call get_ticket_stats 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 tool appears to query and retrieve ticket statistics from the Freshservice platform. The 'get' prefix strongly suggests a read-only operation that retrieves existing data without creating, modifying, or deleting anything. Even if misused by an AI agent, retrieving ticket statistics poses minimal risk—there are no side effects, financial implications, or destructive capabilities.
From the tool's definition Tool name 'get_ticket_stats' contains the verb 'get', which retrieves data. No description provided, but the naming pattern and context within a service management platform indicates this retrieves statistics about tickets without modification.
Attacks that exploit this kind of access
get_ticket_stats. 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 get_ticket_stats: 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.
get_ticket_stats 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 get_ticket_stats 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 get_ticket_stats. 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.
get_ticket_stats 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 →