This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/zip-lookup.md
What zip_lookup does on UnClick
AI agents call zip_lookup 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 |
|---|---|---|---|
code | string | Yes | Zip or postal code |
country | string | — | Country code (default: us). Supports us, gb, au, ca, de, fr, etc. |
Parameters from the server's own tool schema.
Why zip_lookup is rated Low
This tool retrieves geographic or location information based on postal code input. It performs a lookup operation that does not modify, delete, execute code, or move money. The function is purely informational and read-only, making it a Read category risk with low severity.
From the tool's definition Tool name 'zip_lookup' and description 'Look up location info for a zip/postal code' indicate a query/retrieval operation with no side effects.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs zip_lookup 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 zip_lookup, this is the rule to start with:
zip_lookup 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 zip_lookup call is checked against it from then on.
Questions about zip_lookup
Look up location info for a zip/postal code. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
zip_lookup accepts 2 parameters: code, country. Required: code. 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 zip_lookup: 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.
zip_lookup 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 zip_lookup 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 zip_lookup. 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.
zip_lookup 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