zendesk_list_users

List Zendesk users with optional search by email or name.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/zendesk-list-users.md

WHAT IT DOES

What zendesk_list_users does on Integrations MCP

AI agents call zendesk_list_users 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.

RISK

Why zendesk_list_users is rated Low

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

RECOMMENDED RULE

The rule that runs zendesk_list_users 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_list_users, this is the rule to start with:

zendesk_list_users Allowed

zendesk_list_users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zendesk_list_users": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every zendesk_list_users call is checked against it from then on.

FAQ

Questions about zendesk_list_users

What does the zendesk_list_users tool do? +

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.

How do I enforce a policy on zendesk_list_users? +

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.

What risk level is zendesk_list_users? +

zendesk_list_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zendesk_list_users? +

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.

How do I block zendesk_list_users completely? +

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.

What MCP server provides zendesk_list_users? +

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.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →