genderize_predict
Predict gender from a first name with probability score.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/genderize-predict.md
What genderize_predict does on UnClick
AI agents call genderize_predict 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 predict gender for. |
country_id | string | — | ISO 3166-1 alpha-2 country code for localized prediction. |
Parameters from the server's own tool schema.
Why genderize_predict is rated Low
This is a pure read operation: it takes a name as input and returns a prediction result with no side effects, no data modification, no code execution, and no destructive capability. The probability score indicates it's a lookup/inference tool similar to dictionary or knowledge queries. Low severity reflects minimal blast radius even if misused in an AI workflow (e.g., generating demographic predictions).
From the tool's definition Tool performs 'Predict gender from a first name with probability score' — a stateless lookup/inference operation that retrieves probabilistic data without modifying any state, creating accounts, executing code, or affecting external systems.
Attacks that exploit this kind of access
The rule that runs genderize_predict 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_predict, this is the rule to start with:
genderize_predict 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_predict call is checked against it from then on.
Questions about genderize_predict
Predict gender from a first name with probability score. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
genderize_predict 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_predict: 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_predict 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_predict 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_predict. 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_predict 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