List all conversation of a ticket in freshservice.
AI agents call list_all_ticket_conversation 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.
This tool retrieves and displays conversation history associated with a ticket. It is a read-only operation that queries data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an AI agent could retrieve sensitive ticket details from conversations, but cannot change state, trigger external operations, or cause irreversible harm.
From the tool's definition Tool name contains 'list_all' and description states 'List all conversation of a ticket' — retrieves/queries existing ticket conversation data with no modification or side effects.
Attacks that exploit this kind of access
List all conversation of a ticket in freshservice. 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 list_all_ticket_conversation: 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.
list_all_ticket_conversation 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 list_all_ticket_conversation 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 list_all_ticket_conversation. 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.
list_all_ticket_conversation 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 →