address.ukpost.validate
Check if a UK postcode is valid and exists — returns true/false. Use for form validation or data cleaning (Postcodes.io)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/address.ukpost.validate.md
What address.ukpost.validate does on Apibase
AI agents call address.ukpost.validate 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 |
|---|---|---|---|
postcode | string | Yes | UK postcode to validate (e.g. "SW1A 1AA"). Returns true if valid format and exists |
Parameters from the server's own tool schema.
Why address.ukpost.validate is rated Low
Tool validates postcodes without modifying data or triggering external actions; read-only query operation.
From the tool's definition Check if a UK postcode is valid and exists — returns true/false
Attacks that exploit this kind of access
The rule that runs address.ukpost.validate 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.validate, this is the rule to start with:
address.ukpost.validate 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.validate call is checked against it from then on.
Questions about address.ukpost.validate
Check if a UK postcode is valid and exists — returns true/false. Use for form validation or data cleaning (Postcodes.io). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
address.ukpost.validate accepts 1 parameter: postcode. Required: postcode. 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.validate: 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.validate 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.validate 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.validate. 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.validate 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