This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/zip-by-city.md
What zip_by_city does on UnClick
AI agents call zip_by_city 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 |
|---|---|---|---|
city | string | Yes | City name |
state | string | Yes | State abbreviation (e.g. CA, NY) |
country | string | — | Country code (default: us) |
Parameters from the server's own tool schema.
Why zip_by_city is rated Low
This is a straightforward data retrieval tool that queries a postal code database based on city and state parameters. It has no side effects, does not modify data, does not execute code or commands, and does not involve financial transactions. The information being retrieved (zip/postal codes) is public reference data.
From the tool's definition Tool name 'zip_by_city' and description 'Look up zip/postal codes for a city and state' indicate a query operation that retrieves publicly available postal code data without modification, deletion, or external execution.
Attacks that exploit this kind of access
The rule that runs zip_by_city 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_by_city, this is the rule to start with:
zip_by_city 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_by_city call is checked against it from then on.
Questions about zip_by_city
Look up zip/postal codes for a city and state. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
zip_by_city accepts 3 parameters: city, state, country. Required: city, state. 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_by_city: 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_by_city 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_by_city 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_by_city. 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_by_city 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