ine-spain.series.table_data
Get the most-recent data points (1-6 periods, default 1) for EVERY series in a table (table_id from ine-spain.tables). Tables can bundle hundreds of series, so periods is capped tightly — use ine-spain.series_data for a longer single-series history. Data: servicios.ine.es (INE Tempus3 API), no au...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ine-spain.series.table-data.md
What ine-spain.series.table_data does on Apibase
AI agents call ine-spain.series.table_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: ES (Spanish, default) or EN (English). |
periods | integer | — | Number of most-recent periods to return per series, 1-6 (default 1). Tables can bundle hundreds of series, so this is capped tightly to stay under the response |
table_id | integer | Yes | Numeric table id from ine-spain.tables, e.g. 24077 for the national CPI index table. |
Parameters from the server's own tool schema.
Why ine-spain.series.table_data is rated Low
Retrieves public statistical data from INE without authentication or side effects.
From the tool's definition Get the most-recent data points for EVERY series in a table
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ine-spain.series.table_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 ine-spain.series.table_data, this is the rule to start with:
ine-spain.series.table_data 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 ine-spain.series.table_data call is checked against it from then on.
Questions about ine-spain.series.table_data
Get the most-recent data points (1-6 periods, default 1) for EVERY series in a table (table_id from ine-spain.tables). Tables can bundle hundreds of series, so periods is capped tightly — use ine-spain.series_data for a longer single-series history. Data: servicios.ine.es (INE Tempus3 API), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ine-spain.series.table_data accepts 3 parameters: lang, periods, table_id. Required: table_id. 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 ine-spain.series.table_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.
ine-spain.series.table_data 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 ine-spain.series.table_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.
Set action: deny in the PolicyLayer policy for ine-spain.series.table_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.
ine-spain.series.table_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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue