estat-japan-dashboard.reference.indicator_info
Get metadata for one e-Stat Statistics Dashboard indicator code — name, unit, source survey, valid date range, and the cycle/regional-rank combinations it publishes (e.g. Month vs Calendar Year, Japan vs Prefecture). Call this BEFORE estat-japan-dashboard.get_data to confirm units and available c...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/estat-japan-dashboard.reference.indicator-info.md
What estat-japan-dashboard.reference.indicator_info does on Apibase
AI agents call estat-japan-dashboard.reference.indicator_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). |
indicator_code | string | Yes | 20-digit e-Stat Dashboard indicator code to look up, e.g. '0201010000000010000' (total population). Returns the indicator name, unit, source survey, valid date |
Parameters from the server's own tool schema.
Why estat-japan-dashboard.reference.indicator_info is rated Low
Retrieves metadata about statistical indicators with no side effects or data modification capability.
From the tool's definition Get metadata for one e-Stat Statistics Dashboard indicator code — name, unit, source survey, valid date range
Attacks that exploit this kind of access
The rule that runs estat-japan-dashboard.reference.indicator_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.indicator_info, this is the rule to start with:
estat-japan-dashboard.reference.indicator_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.indicator_info call is checked against it from then on.
Questions about estat-japan-dashboard.reference.indicator_info
Get metadata for one e-Stat Statistics Dashboard indicator code — name, unit, source survey, valid date range, and the cycle/regional-rank combinations it publishes (e.g. Month vs Calendar Year, Japan vs Prefecture). Call this BEFORE estat-japan-dashboard.get_data to confirm units and available cycles for the indicator. Data: dashboard.e-stat.go.jp (Japan Ministry of Internal Affairs and Communications), 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.indicator_info accepts 2 parameters: lang, indicator_code. Required: indicator_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.indicator_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.indicator_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.indicator_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.indicator_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.indicator_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