get_zendesk_user
Get a Zendesk user by ID. Returns full user details including name, email, role, phone, organization, and custom fields.
This record as markdown: /tools/freshdesk/get-zendesk-user.md
What get_zendesk_user does on Freshdesk
AI agents call get_zendesk_user 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 get_zendesk_user is rated Low
This tool performs a query operation that retrieves user information from Zendesk without modifying, deleting, or executing any actions. It has no side effects beyond data retrieval. The severity is low because user metadata retrieval poses minimal risk even if accessed by an unauthorized agent, as the data returned is limited to standard user profile fields.
From the tool's definition Tool description states 'Get a Zendesk user by ID' and 'Returns full user details' — a retrieval operation with no modification or side effects. The verb 'Get' and action of returning data are characteristic of Read operations.
Attacks that exploit this kind of access
The rule that runs get_zendesk_user 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 get_zendesk_user, this is the rule to start with:
get_zendesk_user 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 get_zendesk_user call is checked against it from then on.
Questions about get_zendesk_user
Get a Zendesk user by ID. Returns full user details including name, email, role, phone, organization, and custom fields. 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 get_zendesk_user: 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.
get_zendesk_user 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 get_zendesk_user 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 get_zendesk_user. 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.
get_zendesk_user 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