faker_persons
Generate fake person data (name, email, phone, address) for testing.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/faker-persons.md
What faker_persons does on UnClick
AI agents call faker_persons 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 |
|---|---|---|---|
locale | string | — | Locale code (default: en_US). |
quantity | number | — | Number of persons (max 100, default 5). |
Parameters from the server's own tool schema.
Why faker_persons is rated Low
This tool produces fake/synthetic data for testing purposes only. It retrieves or generates harmless test data with no capability to modify, delete, execute code, commit financial actions, or affect real systems. The blast radius of misuse is minimal—worst case, an agent could generate test data unnecessarily, which has no security or operational impact.
From the tool's definition Tool generates synthetic test data (name, email, phone, address) with no modification of real data or side effects. The verb 'generate' combined with 'for testing' indicates data creation that does not persist to external systems or modify existing records.
Attacks that exploit this kind of access
The rule that runs faker_persons 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 faker_persons, this is the rule to start with:
faker_persons 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 faker_persons call is checked against it from then on.
Questions about faker_persons
Generate fake person data (name, email, phone, address) for testing. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
faker_persons accepts 2 parameters: locale, quantity. 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 faker_persons: 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.
faker_persons 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 faker_persons 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 faker_persons. 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.
faker_persons 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