New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about estat-japan-dashboard.reference.indicator_info

What does the estat-japan-dashboard.reference.indicator_info tool do? +

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.

What parameters does estat-japan-dashboard.reference.indicator_info accept? +

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.

How do I enforce a policy on estat-japan-dashboard.reference.indicator_info? +

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.

What risk level is estat-japan-dashboard.reference.indicator_info? +

estat-japan-dashboard.reference.indicator_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit estat-japan-dashboard.reference.indicator_info? +

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.

How do I block estat-japan-dashboard.reference.indicator_info completely? +

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.

What MCP server provides estat-japan-dashboard.reference.indicator_info? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.