Use this when the user asks about people, extensions, or phone users. Searches across extension number, first name, last name, display name, email, and mobile. Examples:
AI agents call find_users to retrieve information from 3CX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
find_users is a search operation that retrieves user information from the 3CX system without modifying, executing, or deleting anything. It has no side effects beyond returning matching records. This is a straightforward Read operation with low severity since it only exposes contact/user directory data that is typically accessed for legitimate administrative purposes.
From the tool's definition Tool description explicitly states it "Searches across extension number, first name, last name, display name, email, and mobile" with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Use this when the user asks about people, extensions, or phone users. Searches across extension number, first name, last name, display name, email, and mobile. Examples:. It is categorised as a Read tool in the 3CX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 3CX MCP Server MCP server in PolicyLayer and add a rule for find_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 3CX MCP Server. Nothing to install.
find_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 find_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 find_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.
find_users is provided by the 3CX MCP Server MCP server (ssig-it/3cx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
find_users is one line of 3CX MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →