get_user

THE RISK

Low Risk

Why get_user needs a policy

This tool retrieves user information by ID with no side effects. It is a simple read operation that queries data without creating, modifying, deleting, or executing anything. The low severity reflects minimal blast radius if misused—at worst, an agent could enumerate or discover user information within the system.

From the tool's definition Tool name is 'get_user' and description states 'Get a User by their ID' — a pure retrieval operation with no modification, deletion, or execution.

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

POLICY

How to control get_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 get_user:

policy.json

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

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Carbon Voice tools

Destructive delete_folder Delete a folder by its ID. Deleting a folder will also delete nested folders and all the m Execute run_ai_action Run an AI Action (Prompt) for a message. You can run an AI Action for a message by its ID Execute run_ai_action_for_shared_link Run an AI Action (Prompt) for a shared link. You can run an AI Action for a shared link by Write add_attachments_to_message Add attachments to a message. In order to add attachments to a message, you must provide a Write create_conversation_message Sends a message to an existing conversation or any type with a conversation_id. Write create_direct_message Send a Direct Message (DM) to a User or a Group of Users. Write create_folder Create a new folder. Write create_voicememo_message Create a VoiceMemo Message. In order to create a VoiceMemo Message, you must provide a tra

All 28 Carbon Voice tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_user

What does the get_user tool do? +

Get a User by their ID. 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 get_user? +

Register the Carbon Voice MCP server in PolicyLayer and add a rule for get_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 get_user? +

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

Can I rate-limit get_user? +

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

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

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

CHECK YOUR STACK →