postcode_lookup
Look up a UK postcode for lat/lon, region, district, ward, and constituency.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/postcode-lookup.md
What postcode_lookup does on UnClick
AI agents call postcode_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 |
|---|---|---|---|
postcode | string | Yes | UK postcode (e.g. SW1A 1AA). |
Parameters from the server's own tool schema.
Why postcode_lookup is rated Low
This is a straightforward data retrieval tool that queries postcode information and returns geographic metadata. It has no side effects, does not modify data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an agent could only retrieve publicly available geographic information about UK locations.
From the tool's definition Tool performs 'Look up' operation on UK postcode data to retrieve lat/lon, region, district, ward, and constituency information. No modification, deletion, or execution described.
Attacks that exploit this kind of access
The rule that runs postcode_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 postcode_lookup, this is the rule to start with:
postcode_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 postcode_lookup call is checked against it from then on.
Questions about postcode_lookup
Look up a UK postcode for lat/lon, region, district, ward, and constituency. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
postcode_lookup accepts 1 parameter: postcode. Required: postcode. 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 postcode_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.
postcode_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 postcode_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 postcode_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.
postcode_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