search_zendesk_users

Search Zendesk users by name, email, or query. Examples: -

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk
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/freshdesk/search-zendesk-users.md

What search_zendesk_users does on Freshdesk

AI agents call search_zendesk_users 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 search_zendesk_users is rated Low

This tool queries existing user data without creating, modifying, deleting, or executing any operations. It has minimal blast radius even if misused by an AI agent, as it only exposes publicly queryable user information in a support system. Severity is low because unauthorized user enumeration is a common and generally low-impact risk in ticketing systems.

From the tool's definition Tool description states 'Search Zendesk users by name, email, or query' — a retrieval operation with no modification or deletion. The verb 'search' and the read-only nature of querying user information confirms this is a Read category tool.

Questions about search_zendesk_users

What does the search_zendesk_users tool do? +

Search Zendesk users by name, email, or query. Examples: -. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_zendesk_users? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for search_zendesk_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 Freshdesk. Nothing to install.

What risk level is search_zendesk_users? +

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

Can I rate-limit search_zendesk_users? +

Yes. Add a rate_limit block to the search_zendesk_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 search_zendesk_users completely? +

Set action: deny in the PolicyLayer policy for search_zendesk_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 search_zendesk_users? +

search_zendesk_users 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Freshdesk's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.