AI agents call random_email 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 |
|---|---|---|---|
safe | boolean | — | Use safe domains (example.com, etc.) vs realistic domains |
count | integer | — | Number of emails to generate |
domain | object | — | Specific domain (e.g., 'example.com') |
locale | object | — | Locale for name-based emails |
Parameters from the server's own tool schema.
This tool generates synthetic data (random email addresses) deterministically without reading from, modifying, or deleting any actual data. It is purely generative and has no destructive or operational side effects. While technically not a 'retrieval' tool, it falls under Read category as the closest fit for safe, read-only operations with no side effects.
From the tool's definition Tool name 'random_email' and description 'Generate random email address(es) using Faker' indicate data generation with no side effects, state changes, or external operations.
Attacks that exploit this kind of access
Generate random email address(es) using Faker. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_email accepts 4 parameters: safe, count, domain, 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_email: 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_email 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_email 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_email. 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_email 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_email 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 →