random_user
Generate random user profiles with names, emails, addresses, and photos.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/random-user.md
What random_user does on UnClick
AI agents call random_user to retrieve information from UnClick 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 | number | — | Number of users to generate (default 1) |
gender | string | — | Filter by gender: male or female |
nationality | string | — | ISO 3166-1 alpha-2 codes, comma-separated (e.g. US,GB,AU) |
Parameters from the server's own tool schema.
Why random_user is rated Low
This tool retrieves (generates and returns) synthetic data with no capability to modify real systems, execute commands, delete data, or commit financial transactions. It is a pure data generation utility that poses minimal security risk—low blast radius even if misused, as outputs are fake profiles with no binding effect on real users or systems.
From the tool's definition Tool generates synthetic random user profiles (names, emails, addresses, photos) with no reference to real data access, modification, or side effects. The description indicates data generation/retrieval of fictional profiles only.
Attacks that exploit this kind of access
The rule that runs random_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For random_user, this is the rule to start with:
random_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every random_user call is checked against it from then on.
Questions about random_user
Generate random user profiles with names, emails, addresses, and photos. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
random_user accepts 3 parameters: count, gender, nationality. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for 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 UnClick. Nothing to install.
random_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
random_user is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue