list_freshdesk_tickets
List Freshdesk tickets using predefined filters. Default:
This record as markdown: /tools/freshdesk/list-freshdesk-tickets.md
What list_freshdesk_tickets does on Freshdesk
AI agents call list_freshdesk_tickets to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_freshdesk_tickets is rated Low
This tool queries and retrieves ticket data from Freshdesk without creating, modifying, deleting, or executing any operations. It is purely a read operation that returns information based on predefined filters. The low severity reflects minimal risk—at worst, an agent could retrieve sensitive ticket information, but cannot alter or delete data.
From the tool's definition Tool name 'list_freshdesk_tickets' and description 'List Freshdesk tickets using predefined filters' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_freshdesk_tickets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_freshdesk_tickets, this is the rule to start with:
list_freshdesk_tickets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every list_freshdesk_tickets call is checked against it from then on.
Questions about list_freshdesk_tickets
List Freshdesk tickets using predefined filters. Default:. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for list_freshdesk_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 Freshdesk. Nothing to install.
list_freshdesk_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 list_freshdesk_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 list_freshdesk_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.
list_freshdesk_tickets is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue