random_address
Generate random address(es) using Faker with locale support.
This record as markdown: /tools/io-tinyfn-tinyfn/random-address.md
What random_address does on TinyFn
AI agents call random_address to retrieve information from TinyFn 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 | integer | — | Number of addresses to generate |
locale | object | — | Locale (e.g., en_US, en_GB, de_DE, ja_JP) |
Parameters from the server's own tool schema.
Why random_address is rated Low
The tool generates random synthetic addresses using a faker library, which is a deterministic data generation operation. It does not query, modify, delete, or execute external operations. It produces fake data as output with no side effects on any system or data store. This aligns with Read category as it is informational/generative in nature with no destructive, financial, or execution risks.
From the tool's definition Tool name 'random_address' and description 'Generate random address(es) using Faker' indicates data generation with no retrieval of real data or side effects. This is a read-like operation that produces synthetic output.
Attacks that exploit this kind of access
The rule that runs random_address safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For random_address, this is the rule to start with:
random_address 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 TinyFn, apply this rule, and every random_address call is checked against it from then on.
Questions about random_address
Generate random address(es) 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_address accepts 2 parameters: count, 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_address: 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_address 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_address 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_address. 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_address 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.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue