postcode-japan.postal.search
Search Japanese postcodes by free-text query, prefecture code (1–47), or city name. Returns matching postcodes with full address in kanji, kana, and romaji, plus coordinates. Useful for address autocomplete, geocoding Japanese locations, and finding all postcodes in a given area. Queries can mix ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/postcode-japan.postal.search.md
What postcode-japan.postal.search does on Apibase
AI agents call postcode-japan.postal.search 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 |
|---|---|---|---|
city | string | — | Filter by city name in Japanese (e.g. "渋谷区" for Shibuya ward, "大阪市北区" for Kita-ku Osaka). |
limit | integer | — | Maximum number of results to return (1–100, default 20). |
query | string | — | Free-text search string in Japanese (kanji/kana) or romaji (e.g. "渋谷" for Shibuya, "Shinjuku", "銀座"). Matched against prefecture, city, and suburb fields. |
prefecture | string | number | — | Filter by prefecture JIS code (1–47) or prefecture name in Japanese (e.g. 13 or "東京都" for Tokyo, 27 for Osaka). Use the prefectures tool to get all codes. |
Parameters from the server's own tool schema.
Why postcode-japan.postal.search is rated Low
Tool retrieves postcode data without modifying any state or triggering external operations.
From the tool's definition Search Japanese postcodes, returns matching postcodes with address and coordinates
Attacks that exploit this kind of access
The rule that runs postcode-japan.postal.search 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.search, this is the rule to start with:
postcode-japan.postal.search 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.search call is checked against it from then on.
Questions about postcode-japan.postal.search
Search Japanese postcodes by free-text query, prefecture code (1–47), or city name. Returns matching postcodes with full address in kanji, kana, and romaji, plus coordinates. Useful for address autocomplete, geocoding Japanese locations, and finding all postcodes in a given area. Queries can mix Japanese (kanji/kana) and romaji. Filter by prefecture JIS code (e.g. 13 for Tokyo, 27 for Osaka) or city name in Japanese. 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.search accepts 4 parameters: city, limit, query, prefecture. 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.search: 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.search 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.search 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.search. 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.search 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