list_zendesk_views
List available ticket views in Zendesk. Views are saved searches/filters that organize tickets. Returns: - View ID, title, and active status - Whether the view is shared or personal Use views to efficiently find tickets by pre-defined criteria like
This record as markdown: /tools/freshdesk/list-zendesk-views.md
What list_zendesk_views does on Freshdesk
AI agents call list_zendesk_views 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_zendesk_views is rated Low
This is a read-only operation that retrieves and lists existing Zendesk views without creating, modifying, deleting, executing code, or affecting financial systems. The blast radius of misuse is minimal—an agent could enumerate views to understand ticket organization, but cannot damage data or trigger side effects.
From the tool's definition The tool name 'list_zendesk_views' and description clearly indicate it lists available ticket views and returns metadata like View ID, title, active status, and sharing information.
Attacks that exploit this kind of access
The rule that runs list_zendesk_views 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_zendesk_views, this is the rule to start with:
list_zendesk_views 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_zendesk_views call is checked against it from then on.
Questions about list_zendesk_views
List available ticket views in Zendesk. Views are saved searches/filters that organize tickets. Returns: - View ID, title, and active status - Whether the view is shared or personal Use views to efficiently find tickets by pre-defined criteria like. 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_zendesk_views: 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_zendesk_views 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_zendesk_views 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_zendesk_views. 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_zendesk_views 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