zendesk_get_user
Get a single Zendesk user by ID.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/zendesk-get-user.md
What zendesk_get_user does on Integrations MCP
AI agents call zendesk_get_user to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why zendesk_get_user is rated Low
This tool retrieves user information from Zendesk without creating, modifying, or deleting data. The 'Get' verb and the explicit purpose of fetching a single user record by identifier classify this as a Read operation. Severity is low because retrieval of user metadata poses minimal direct risk; exposure depends on what user data is accessible, but the operation itself is non-destructive and reversible.
From the tool's definition Tool name 'zendesk_get_user' and description 'Get a single Zendesk user by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs zendesk_get_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zendesk_get_user, this is the rule to start with:
zendesk_get_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 Integrations MCP, apply this rule, and every zendesk_get_user call is checked against it from then on.
Questions about zendesk_get_user
Get a single Zendesk user by ID. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for zendesk_get_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 Integrations MCP. Nothing to install.
zendesk_get_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 zendesk_get_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 zendesk_get_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.
zendesk_get_user is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue