ine-spain.series.data
Get up to 100 most-recent data points plus rich metadata (period name, provisional flag) for ONE specific series (series_code, e.g. "IPC251856" — from an ine-spain.table_data result COD field or the INE website). An unrecognized series_code returns an empty upstream response. Data: servicios.ine....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ine-spain.series.data.md
What ine-spain.series.data does on Apibase
AI agents call ine-spain.series.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, 1-100 (default 12). |
series_code | string | Yes | Series code, e.g. "IPC251856" (from a table_data result COD field, or the INE website). An unrecognized code returns an empty response. |
Parameters from the server's own tool schema.
Why ine-spain.series.data is rated Low
Retrieves historical economic data from INE with no side effects or modification capability.
From the tool's definition Get up to 100 most-recent data points plus rich metadata for ONE specific series
Attacks that exploit this kind of access
The rule that runs ine-spain.series.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.data, this is the rule to start with:
ine-spain.series.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.data call is checked against it from then on.
Questions about ine-spain.series.data
Get up to 100 most-recent data points plus rich metadata (period name, provisional flag) for ONE specific series (series_code, e.g. "IPC251856" — from an ine-spain.table_data result COD field or the INE website). An unrecognized series_code returns an empty upstream response. 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.data accepts 3 parameters: lang, periods, series_code. Required: series_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 ine-spain.series.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.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.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.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.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