List Zendesk users with optional search by email or name.
AI agents call zendesk_list_users to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from Zendesk without creating, modifying, or deleting any data. The search parameters (email, name) are read-only filters. The blast radius is minimal — an AI agent misusing this could retrieve user lists but cannot cause harm beyond potential information exposure depending on data sensitivity and access controls.
From the tool's definition Tool name contains 'list' and description states 'List Zendesk users with optional search by email or name' — pure data retrieval with no modification or side effects.
Attacks that exploit this kind of access
List Zendesk users with optional search by email or name. 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_list_users: 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_list_users 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_list_users 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_list_users. 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_list_users 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →