lorem_name_generate
Generate random placeholder names with optional email addresses.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/lorem-name-generate.md
What lorem_name_generate does on UnClick
AI agents call lorem_name_generate to retrieve information from UnClick 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 | number | — | Number of names (1-50, default 1). |
email | boolean | — | Include email addresses (default true). |
domain | string | — | Email domain (default example.com). |
Parameters from the server's own tool schema.
Why lorem_name_generate is rated Low
This tool generates synthetic/random placeholder data (names and email addresses). It has no side effects, does not read from or write to any external system, and produces harmless dummy content. Classified as Read (data generation with no external state changes), with low severity since misuse risk is minimal.
From the tool's definition Generate random placeholder names with optional email addresses
Attacks that exploit this kind of access
The rule that runs lorem_name_generate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lorem_name_generate, this is the rule to start with:
lorem_name_generate 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 UnClick, apply this rule, and every lorem_name_generate call is checked against it from then on.
Questions about lorem_name_generate
Generate random placeholder names with optional email addresses. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
lorem_name_generate accepts 3 parameters: count, email, domain. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for lorem_name_generate: 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 UnClick. Nothing to install.
lorem_name_generate 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 lorem_name_generate 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 lorem_name_generate. 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.
lorem_name_generate is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue