genderize_name
Predict the gender of a person based on their first name.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/genderize-name.md
What genderize_name does on UnClick
AI agents call genderize_name 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 |
|---|---|---|---|
name | string | Yes | First name to analyze |
country_id | string | — | ISO 3166-1 alpha-2 country code for localization |
Parameters from the server's own tool schema.
Why genderize_name is rated Low
This tool takes a name as input and returns a prediction—a pure read operation that queries data (likely a statistical database of name-gender associations) without altering state, executing code, or triggering external actions. The blast radius of misuse is minimal; worst case, an AI agent generates inaccurate gender predictions, which is informational rather than operationally harmful.
From the tool's definition Tool performs prediction based on input name without modifying, deleting, or executing external operations. Description states 'Predict the gender' which is a retrieval/analysis operation with no side effects.
Attacks that exploit this kind of access
The rule that runs genderize_name 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 genderize_name, this is the rule to start with:
genderize_name 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 genderize_name call is checked against it from then on.
Questions about genderize_name
Predict the gender of a person based on their first name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
genderize_name accepts 2 parameters: name, country_id. Required: name. 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 genderize_name: 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.
genderize_name 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 genderize_name 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 genderize_name. 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.
genderize_name 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