postcode-japan.postal.lookup
Look up a Japanese postal address by its 7-digit postcode. Returns prefecture, city, suburb, and street-level address in Japanese kanji, hiragana/katakana readings, and romaji, plus JIS administrative code and GPS coordinates. Accepts codes with or without hyphen (e.g. "1500001" or "150-0001"). C...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/postcode-japan.postal.lookup.md
What postcode-japan.postal.lookup does on Apibase
AI agents call postcode-japan.postal.lookup 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 | Japanese 7-digit postal code with or without hyphen (e.g. "1000001" or "100-0001" for Chiyoda, "1500001" for Shibuya Jinguumae). Hyphens and spaces are stripped |
Parameters from the server's own tool schema.
Why postcode-japan.postal.lookup is rated Low
Tool retrieves postal address data from postcode lookup; read-only with no side effects or data modification.
From the tool's definition Look up a Japanese postal address by its 7-digit postcode. Returns prefecture, city, suburb, street-level address.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs postcode-japan.postal.lookup 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 postcode-japan.postal.lookup, this is the rule to start with:
postcode-japan.postal.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 Apibase, apply this rule, and every postcode-japan.postal.lookup call is checked against it from then on.
Questions about postcode-japan.postal.lookup
Look up a Japanese postal address by its 7-digit postcode. Returns prefecture, city, suburb, and street-level address in Japanese kanji, hiragana/katakana readings, and romaji, plus JIS administrative code and GPS coordinates. Accepts codes with or without hyphen (e.g. "1500001" or "150-0001"). Coverage: all ~124,000 active Japan Post postcodes, updated regularly. Data source: postcode.teraren.com — MIT license, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
postcode-japan.postal.lookup 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 postcode-japan.postal.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 Apibase. Nothing to install.
postcode-japan.postal.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-japan.postal.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-japan.postal.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-japan.postal.lookup 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