estat-japan-dashboard.series.get_data

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 61 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.series.get-data.md

WHAT IT DOES

What estat-japan-dashboard.series.get_data does on Apibase

AI agents call estat-japan-dashboard.series.get_data 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).
`cycle`	string	—	Filter to one reporting cycle when an indicator publishes more than one, e.g. '1' (Month) or '3' (Calendar Year). See the cycle codes returned by estat-japan-da
`time_to`	string	—	End of the time range, same notation as time_from, e.g. '2022CY00'.
`time_from`	string	—	Start of the time range, in the indicator's own cycle notation, e.g. '2020CY00' (calendar year 2020) or '202101' + '00' -> '20210100' (January 2021 for monthly
`region_code`	string	—	Region code to filter by. '00000' = Japan (national total, default upstream behaviour if omitted returns all regions the indicator has data for). 5-digit codes
`indicator_code`	string	Yes	20-digit e-Stat Dashboard indicator code, e.g. '0201010000000010000' (total population). Comma-separate multiple codes to fetch several series in one call. Disc

Parameters from the server's own tool schema.

RISK

Why estat-japan-dashboard.series.get_data is rated Low

Retrieves historical statistical data without modifying state or triggering external operations.

From the tool's definition Fetch time-series values for one or more e-Stat Statistics Dashboard indicator codes

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs estat-japan-dashboard.series.get_data 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.series.get_data, this is the rule to start with:

estat-japan-dashboard.series.get_data Allowed

estat-japan-dashboard.series.get_data is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "estat-japan-dashboard.series.get_data": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every estat-japan-dashboard.series.get_data call is checked against it from then on.

FAQ

Questions about estat-japan-dashboard.series.get_data

What does the estat-japan-dashboard.series.get_data tool do? +

Fetch time-series values for one or more e-Stat Statistics Dashboard indicator codes, optionally filtered by region and time range — population, labour, economy, trade, and other official Japanese government statistics (and comparable world figures for some indicators). Always call estat-japan-dashboard.indicator_info first to confirm units and valid cycle for the indicator, and estat-japan-dashboard.region_info to confirm region codes. Example: total population (indicator_code='0201010000000010000'), Japan (region_code='00000'), 2020-2022 (time_from='2020CY00', time_to='2022CY00'). Data: dashboard.e-stat.go.jp, no auth required, Public Data License v1.0 (attribution required, commercial reuse permitted). 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.series.get_data accept? +

estat-japan-dashboard.series.get_data accepts 6 parameters: lang, cycle, time_to, time_from, region_code, 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.series.get_data? +

Register the Apibase MCP server in PolicyLayer and add a rule for estat-japan-dashboard.series.get_data: 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.series.get_data? +

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

Can I rate-limit estat-japan-dashboard.series.get_data? +

Yes. Add a rate_limit block to the estat-japan-dashboard.series.get_data 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.series.get_data completely? +

Set action: deny in the PolicyLayer policy for estat-japan-dashboard.series.get_data. 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.series.get_data? +

estat-japan-dashboard.series.get_data 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →