postcode-japan.reference.prefectures
Get the complete list of all 47 Japanese prefectures with JIS codes, official names in kanji, hiragana, katakana, and English, plus geographic region. Use prefecture codes returned here as the "prefecture" filter in the postcode-japan.postal.search tool. Data source: postcode.teraren.com — MIT li...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/postcode-japan.reference.prefectures.md
What postcode-japan.reference.prefectures does on Apibase
AI agents call postcode-japan.reference.prefectures 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 |
|---|---|---|---|
_placeholder | string | — | No parameters required. Returns all 47 Japanese prefectures with JIS code, names in kanji, hiragana, katakana, English, and region. |
Parameters from the server's own tool schema.
Why postcode-japan.reference.prefectures is rated Low
Retrieves static reference data about Japanese prefectures with no side effects or mutations.
From the tool's definition Get the complete list of all Japanese prefectures with codes and names.
Attacks that exploit this kind of access
The rule that runs postcode-japan.reference.prefectures 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.reference.prefectures, this is the rule to start with:
postcode-japan.reference.prefectures 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.reference.prefectures call is checked against it from then on.
Questions about postcode-japan.reference.prefectures
Get the complete list of all 47 Japanese prefectures with JIS codes, official names in kanji, hiragana, katakana, and English, plus geographic region. Use prefecture codes returned here as the "prefecture" filter in the postcode-japan.postal.search tool. 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.reference.prefectures accepts 1 parameter: _placeholder. 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.reference.prefectures: 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.reference.prefectures 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.reference.prefectures 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.reference.prefectures. 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.reference.prefectures 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