list_zendesk_accounts
List connected Zendesk accounts with authentication status. Returns all authenticated Zendesk subdomains with their associated email addresses, auth type, and status. Auth types:
This record as markdown: /tools/freshdesk/list-zendesk-accounts.md
What list_zendesk_accounts does on Freshdesk
AI agents call list_zendesk_accounts 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_accounts is rated Low
This tool only retrieves and queries configuration or account data without making any changes, executing commands, or triggering operations. Listing accounts is a read-only operation. The low severity reflects minimal blast radius—enumeration of account metadata poses limited risk even if misused by an agent.
From the tool's definition Tool description explicitly states it 'List[s] connected Zendesk accounts' and 'Returns all authenticated Zendesk subdomains with their associated email addresses, auth type, and status.' The verb 'list' and 'returns' indicate a retrieval operation with no…
Attacks that exploit this kind of access
The rule that runs list_zendesk_accounts 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_accounts, this is the rule to start with:
list_zendesk_accounts 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_accounts call is checked against it from then on.
Questions about list_zendesk_accounts
List connected Zendesk accounts with authentication status. Returns all authenticated Zendesk subdomains with their associated email addresses, auth type, and status. Auth types:. 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_accounts: 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_accounts 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_accounts 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_accounts. 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_accounts 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