test.random.user

Generate realistic random user profiles — name, email, phone, address, age, gender, photo. Filter by nationality and gender. For testing and demo data (RandomUser.me)

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/test.random.user.md

WHAT IT DOES

What test.random.user does on Apibase

AI agents call test.random.user to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`count`	integer	—	Number of random users to generate (default 1, max 20)
`gender`	string	—	Gender filter
`nationality`	string	—	Nationality filter — comma-separated ISO codes (e.g. "us", "gb,fr,de")

Parameters from the server's own tool schema.

RISK

Why test.random.user is rated Low

Tool generates synthetic test data only; no real data access, creation, or modification occurs.

From the tool's definition Generate realistic random user profiles for testing and demo data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs test.random.user safely

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

test.random.user Allowed

test.random.user 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": {
    "test.random.user": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every test.random.user call is checked against it from then on.

FAQ

Questions about test.random.user

What does the test.random.user tool do? +

Generate realistic random user profiles — name, email, phone, address, age, gender, photo. Filter by nationality and gender. For testing and demo data (RandomUser.me). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does test.random.user accept? +

test.random.user accepts 3 parameters: count, gender, nationality. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on test.random.user? +

Register the Apibase MCP server in PolicyLayer and add a rule for test.random.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 Apibase. Nothing to install.

What risk level is test.random.user? +

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

Can I rate-limit test.random.user? +

Yes. Add a rate_limit block to the test.random.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 test.random.user completely? +

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

test.random.user is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

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