AI agents call random_name 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 |
|---|---|---|---|
type | string | — | Name type: first, last, full, prefix, suffix |
count | integer | — | Number of names 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, fr_FR, de_DE) |
Parameters from the server's own tool schema.
This is a pure data generation utility that retrieves/produces information on demand without modifying system state or external resources. It fits the 'Read' category as it has no side effects beyond returning a value. Severity is low because misuse would only produce unwanted random names, with negligible blast radius or security risk.
From the tool's definition Tool generates random names using Faker library with locale support. The description indicates it produces deterministic output (per the server's stated purpose of '500+ deterministic tools') with no side effects—it merely returns generated data without…
Attacks that exploit this kind of access
Generate random name(s) using Faker with locale support. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_name accepts 4 parameters: type, 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_name: 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_name 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_name 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_name. 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_name 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_name 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 →