Low Risk

get_user

Retrieve user profile

How to control get_user ↓

What get_user does on Voyp MCP Server

AI agents call get_user to retrieve information from Voyp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_user needs a policy

The tool retrieves user profile data, which is a read-only operation. Severity is medium rather than low because user profiles typically contain PII or sensitive account information that could be misused if accessed without authorization, but the tool itself performs no destructive or financial actions. Confidence is 0.85 because the description is minimal but the intent is clear from the name and verb 'retrieve'.

From the tool's definition Tool name is 'get_user' with description 'Retrieve user profile' — clearly a data retrieval operation with no modification or side effects.

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

How to control get_user

PolicyLayer is an MCP gateway — it sits between your AI agents and Voyp MCP Server, 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.

  1. Create a free account and register Voyp MCP Server — 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 get_user

What does the get_user tool do? +

Retrieve user profile. It is categorised as a Read tool in the Voyp MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user? +

Register the Voyp MCP Server 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 Voyp MCP Server. 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 Voyp MCP Server MCP server (paulotaylor/voyp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Voyp MCP Server tool call.

Start from Voyp MCP Server, 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.

7 Voyp MCP Server 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.