Low Risk

search_user

Search for a User by their phone number, email address, id or name.

How to control search_user ↓

What search_user does on Carbon Voice

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

Low Risk

Why search_user needs a policy

This tool retrieves user data based on search criteria (phone number, email, id, or name) but does not create, modify, delete, or execute any actions. It is a standard read/query operation with minimal blast radius—an AI misuse would result in unauthorized information disclosure rather than data loss, financial impact, or system compromise.

From the tool's definition Tool name is 'search_user' and description states 'Search for a User' — a query operation that retrieves user information without modification.

Documented attack patterns abuse exactly the kind of access search_user gives an agent:

How to control search_user

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_user:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_user": {}
  }
}

search_user is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Carbon Voice — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_user

What does the search_user tool do? +

Search for a User by their phone number, email address, id or name. It is categorised as a Read tool in the Carbon Voice MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_user? +

Register the Carbon Voice MCP server in PolicyLayer and add a rule for search_user: 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.

What risk level is search_user? +

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

Can I rate-limit search_user? +

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

Set action: deny in the PolicyLayer policy for search_user. 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_user? +

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

Enforce policy on every Carbon Voice tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.