generate_names

Generate random placeholder names.

SERVERTinyFn SOURCEhttps://api.tinyfn.io/mcp/all/

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-tinyfn-tinyfn/generate-names.md

WHAT IT DOES

What generate_names does on TinyFn

AI agents call generate_names 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 names
`include_last`	boolean	—	Include last names

Parameters from the server's own tool schema.

RISK

Why generate_names is rated Low

This tool generates random placeholder names, which is a deterministic or pseudo-random read/compute operation. It does not modify any data, execute code, delete anything, or involve financial transactions. The server context confirms it hosts deterministic utility tools. Severity is low as misuse has negligible blast radius.

From the tool's definition Generate random placeholder names — purely generative/read operation with no side effects, data modification, or external calls

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs generate_names 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 generate_names, this is the rule to start with:

generate_names Allowed

generate_names is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_names": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every generate_names call is checked against it from then on.

FAQ

Questions about generate_names

What does the generate_names tool do? +

Generate random placeholder names. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.

What parameters does generate_names accept? +

generate_names accepts 2 parameters: count, include_last. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on generate_names? +

Register the TinyFn MCP server in PolicyLayer and add a rule for generate_names: 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.

What risk level is generate_names? +

generate_names is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit generate_names? +

Yes. Add a rate_limit block to the generate_names 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.

How do I block generate_names completely? +

Set action: deny in the PolicyLayer policy for generate_names. 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.

What MCP server provides generate_names? +

generate_names 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.

KEEP EXPLORING

More on TinyFn, and thousands of servers like it.

This server

All 572 TinyFn tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →