estat-japan-dashboard.reference.region_info
Get metadata for one e-Stat Statistics Dashboard region code (name, level, valid date range), or omit region_code to fetch the full region catalog — Japan, its 47 prefectures and municipalities, plus world countries used for international-comparison indicators. Use this to discover region codes f...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/estat-japan-dashboard.reference.region-info.md
What estat-japan-dashboard.reference.region_info does on Apibase
AI agents call estat-japan-dashboard.reference.region_info 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 |
|---|---|---|---|
lang | string | — | Response language: 'EN' (English, default) or 'JP' (Japanese). |
region_code | string | — | Region code to look up, e.g. '13000' (Tokyo) or '00000' (Japan). Omit to fetch the full region catalog (Japan + prefectures + municipalities + world countries) |
Parameters from the server's own tool schema.
Why estat-japan-dashboard.reference.region_info is rated Low
Retrieves region metadata and catalog information with no side effects or data modification capability.
From the tool's definition Get metadata, fetch full region catalog, discover region codes
Attacks that exploit this kind of access
The rule that runs estat-japan-dashboard.reference.region_info 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 estat-japan-dashboard.reference.region_info, this is the rule to start with:
estat-japan-dashboard.reference.region_info 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 estat-japan-dashboard.reference.region_info call is checked against it from then on.
Questions about estat-japan-dashboard.reference.region_info
Get metadata for one e-Stat Statistics Dashboard region code (name, level, valid date range), or omit region_code to fetch the full region catalog — Japan, its 47 prefectures and municipalities, plus world countries used for international-comparison indicators. Use this to discover region codes for estat-japan-dashboard.get_data. Data: dashboard.e-stat.go.jp, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
estat-japan-dashboard.reference.region_info accepts 2 parameters: lang, region_code. 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 estat-japan-dashboard.reference.region_info: 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.
estat-japan-dashboard.reference.region_info 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 estat-japan-dashboard.reference.region_info 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 estat-japan-dashboard.reference.region_info. 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.
estat-japan-dashboard.reference.region_info 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