Search multiple Users by their phone numbers, email addresses, ids or names.
AI agents call search_users to retrieve information from Carbon Voice 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 based on search criteria (phone numbers, emails, IDs, or names) with no side effects. It performs a query operation that returns data without creating, modifying, deleting, or executing any actions. The server description context of messaging and voice memos does not change the nature of this specific tool, which is purely a read/lookup operation.
From the tool's definition Tool description states 'Search multiple Users by their phone numbers, email addresses, ids or names.' The verb 'Search' and the read-only nature of querying user data without modification indicates a retrieval operation.
Documented attack patterns abuse exactly the kind of access search_users gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Carbon Voice, and nothing reaches the server without passing your rules. This is the rule we recommend for search_users:
{
"version": "1",
"default": "deny",
"tools": {
"search_users": {}
}
} search_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search multiple Users by their phone numbers, email addresses, ids or names. It is categorised as a Read tool in the Carbon Voice MCP Server, which means it retrieves data without modifying state.
Register the Carbon Voice MCP server in PolicyLayer and add a rule for search_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 Carbon Voice. Nothing to install.
search_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 search_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 search_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.
search_users is provided by the Carbon Voice MCP server (phononx/cv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Carbon Voice, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 Carbon Voice tools catalogued and risk-classified — across an index of 43,000+ MCP servers.