retrieve_users

Retrieve a specific user.\r\n\r\n\r\n<h4>Required permission(s):</h4><span class=

SERVERWpm Mcp Server SOURCEwpm-mcp-server-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/wpm-mcp-server/retrieve-users.md

WHAT IT DOES

What retrieve_users does on Wpm Mcp Server

AI agents call retrieve_users to retrieve information from Wpm Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why retrieve_users is rated Low

The verb 'retrieve' combined with the singular action of fetching a specific user record indicates this is a read-only operation that queries data without side effects. No creation, modification, deletion, or financial operation is implied. The tool's presence alongside write/destructive tools (create_*, clear_*, auto_payments_) on the same server confirms this is the read category.

From the tool's definition Tool name is 'retrieve_users' with description starting 'Retrieve a specific user' — indicates a query operation with no state modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs retrieve_users safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wpm Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For retrieve_users, this is the rule to start with:

retrieve_users Allowed

retrieve_users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wpm Mcp Server, apply this rule, and every retrieve_users call is checked against it from then on.

FAQ

Questions about retrieve_users

What does the retrieve_users tool do? +

Retrieve a specific user.\r\n\r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Read tool in the Wpm Mcp Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retrieve_users? +

Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for retrieve_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 Wpm Mcp Server. Nothing to install.

What risk level is retrieve_users? +

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

Can I rate-limit retrieve_users? +

Yes. Add a rate_limit block to the retrieve_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.

How do I block retrieve_users completely? +

Set action: deny in the PolicyLayer policy for retrieve_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.

What MCP server provides retrieve_users? +

retrieve_users is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wpm Mcp Server, and thousands of servers like it.

This server

All 420 Wpm Mcp Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →