address.ukpost.nearest
Find nearest UK postcodes to a lat/lon coordinate — returns postcodes sorted by distance with district info. Use for reverse geocoding in the UK (Postcodes.io)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/address.ukpost.nearest.md
What address.ukpost.nearest does on Apibase
AI agents call address.ukpost.nearest to retrieve information from Apibase 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 |
|---|---|---|---|
lat | number | Yes | Latitude (e.g. 51.5074 for London) |
lon | number | Yes | Longitude (e.g. -0.1278 for London) |
limit | integer | — | Max results (1-10, default 5) |
Parameters from the server's own tool schema.
Why address.ukpost.nearest is rated Low
Retrieves postcode data via reverse geocoding; no modifications, deletions, or external operations triggered.
From the tool's definition Find nearest UK postcodes to a lat/lon coordinate — returns postcodes
Attacks that exploit this kind of access
The rule that runs address.ukpost.nearest safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For address.ukpost.nearest, this is the rule to start with:
address.ukpost.nearest 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 Apibase, apply this rule, and every address.ukpost.nearest call is checked against it from then on.
Questions about address.ukpost.nearest
Find nearest UK postcodes to a lat/lon coordinate — returns postcodes sorted by distance with district info. Use for reverse geocoding in the UK (Postcodes.io). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
address.ukpost.nearest accepts 3 parameters: lat, lon, limit. Required: lat, lon. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for address.ukpost.nearest: 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 Apibase. Nothing to install.
address.ukpost.nearest 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 address.ukpost.nearest 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 address.ukpost.nearest. 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.
address.ukpost.nearest is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue