AI agents call random_person to retrieve information from TinyFn without modifying anything — 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 people to generate |
gender | object | — | Gender hint: male, female, or null for random |
locale | object | — | Locale (e.g., en_US, es_ES, ja_JP, zh_CN) |
Parameters from the server's own tool schema.
This tool produces artificial person profiles (names, addresses, etc.) from a Faker library. It retrieves/generates random data without creating, modifying, deleting, or executing external operations. While it generates data rather than querying existing data, it has no side effects and cannot affect real systems or data.
From the tool's definition Tool description states 'Generate complete random person profile(s) using Faker' — generates synthetic, randomized data with no persistence, modification of existing data, or external side effects.
Attacks that exploit this kind of access
Generate complete random person profile(s) using Faker. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_person accepts 3 parameters: count, gender, locale. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for random_person: 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 TinyFn. Nothing to install.
random_person 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_person 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_person. 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_person is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
random_person is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →