random_company
Generate random company name(s) using Faker.
This record as markdown: /tools/io-tinyfn-tinyfn/random-company.md
What random_company does on TinyFn
AI agents call random_company 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 companies to generate |
locale | object | — | Locale (e.g., en_US, ja_JP, de_DE) |
Parameters from the server's own tool schema.
Why random_company is rated Low
This is a data generation/lookup tool that returns synthetic, procedurally-generated data with no side effects. It neither retrieves from nor modifies any persistent state, executes code, nor creates obligations. The worst-case misuse would be generating spurious company names for benign purposes (documentation, examples), which poses minimal risk.
From the tool's definition Tool generates random company names using Faker; described as 'Generate random company name(s)'. No modification, deletion, execution of external code, or financial operations are involved.
Attacks that exploit this kind of access
The rule that runs random_company 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_company, this is the rule to start with:
random_company 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_company call is checked against it from then on.
Questions about random_company
Generate random company name(s) using Faker. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_company 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_company: 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_company 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_company 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_company. 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_company 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