getRandomUsers
Generates fake user profiles such as name, email, address and username for testing or placeholders, with count, gender, age, locale, field selection and seed options.
This record as markdown: /tools/com-api-ninjas-mcp/getrandomusers.md
What getRandomUsers does on API Ninjas
AI agents call getRandomUsers to retrieve information from API Ninjas 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 |
|---|---|---|---|
seed | string | — | Seed value for reproducible random data generation |
count | integer | — | Number of users to generate (1-10000) |
fields | string | — | Comma-separated list of fields to include. If not specified, all available fields are returned. |
gender | string | — | Filter by gender |
locale | string | — | Locale for generating localized data (e.g., en_US, de_DE, fr_FR) |
exclude | string | — | Comma-separated list of fields to exclude from the response |
max_age | integer | — | Maximum age (0-115) |
min_age | integer | — | Minimum age (0-115) |
nationality | string | — | Nationality filter |
password_length | integer | — | Length of generated passwords (6-128) |
blank_percentage | integer | — | Percentage of fields to leave blank (0-100) |
Parameters from the server's own tool schema.
Why getRandomUsers is rated Low
Even though getRandomUsers only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs getRandomUsers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getRandomUsers, this is the rule to start with:
getRandomUsers 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 API Ninjas, apply this rule, and every getRandomUsers call is checked against it from then on.
Questions about getRandomUsers
Generates fake user profiles such as name, email, address and username for testing or placeholders, with count, gender, age, locale, field selection and seed options. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getRandomUsers accepts 11 parameters: seed, count, fields, gender, locale, exclude, max_age, min_age, nationality, password_length, blank_percentage. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getRandomUsers: 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 API Ninjas. Nothing to install.
getRandomUsers 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 getRandomUsers 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 getRandomUsers. 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.
getRandomUsers is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue