export_zendesk_tickets
Export Zendesk tickets using cursor-based pagination with NO 1000-result limit. Use this instead of search_zendesk_tickets when you need MORE than 1000 results, such as bulk exports or comprehensive data analysis. Uses the Zendesk Search Export API (/search/export.json) which supports unlimited r...
This record as markdown: /tools/freshdesk/export-zendesk-tickets.md
What export_zendesk_tickets does on Freshdesk
AI agents call export_zendesk_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 export_zendesk_tickets is rated Low
This tool retrieves/exports ticket data from Zendesk without modifying or deleting anything. It is a bulk read operation. Severity is medium because it can export large volumes of potentially sensitive support ticket data, and the 'save_to_file=true' option writes results to disk, but there are no write/destructive side effects on the source system.
From the tool's definition Export Zendesk tickets using cursor-based pagination with NO 1000-result limit... Uses the Zendesk Search Export API (/search/export.json) which supports unlimited results via cursor-based pagination. Auto-paginates through all matching results.
Attacks that exploit this kind of access
The rule that runs export_zendesk_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 export_zendesk_tickets, this is the rule to start with:
export_zendesk_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 export_zendesk_tickets call is checked against it from then on.
Questions about export_zendesk_tickets
Export Zendesk tickets using cursor-based pagination with NO 1000-result limit. Use this instead of search_zendesk_tickets when you need MORE than 1000 results, such as bulk exports or comprehensive data analysis. Uses the Zendesk Search Export API (/search/export.json) which supports unlimited results via cursor-based pagination. Auto-paginates through all matching results. For bulk analysis (>100 tickets), use save_to_file=true to write results to a JSON file instead of returning them in the conversation. This avoids context overflow and enables processing thousands of tickets via scripts (grep, jq, Node.js). IMPORTANT: Exports with more than 500 results REQUIRE save_to_file=true. The tool will reject large in-context exports to prevent context overflow. Key differences from search_zendesk_tickets: - No 1000-result ceiling (search_zendesk_tickets is capped at 1000) - Always auto-paginates (no manual page parameter) - Results are always sorted by created_at (no custom sort options) - Slightly higher latency per page due to cursor overhead - Has a safety cap (max_results, default 10000) to prevent runaway pagination Query syntax is the same as search_zendesk_tickets (e.g.,. 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 export_zendesk_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.
export_zendesk_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 export_zendesk_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 export_zendesk_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.
export_zendesk_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