ine.reference.tables
List the published data tables for a Spanish INE statistical operation (e.g. "IPC", "EPA"), including periodicity, publication name, and start period. Use an operation_code from ine.operations. Data: servicios.ine.es (INE Tempus3 API), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ine.reference.tables.md
What ine.reference.tables does on Apibase
AI agents call ine.reference.tables 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 |
|---|---|---|---|
operation_code | string | Yes | Short code of the statistical operation, from ine.operations (e.g. "IPC" for Consumer Price Index, "EPA" for Labour Force Survey). |
Parameters from the server's own tool schema.
Why ine.reference.tables is rated Low
Read-only listing of Spanish INE statistical tables with no side effects.
From the tool's definition List the published data tables... no auth required
Attacks that exploit this kind of access
The rule that runs ine.reference.tables 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.reference.tables, this is the rule to start with:
ine.reference.tables 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.reference.tables call is checked against it from then on.
Questions about ine.reference.tables
List the published data tables for a Spanish INE statistical operation (e.g. "IPC", "EPA"), including periodicity, publication name, and start period. Use an operation_code from ine.operations. 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.reference.tables accepts 1 parameter: operation_code. Required: operation_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.reference.tables: 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.reference.tables 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.reference.tables 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.reference.tables. 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.reference.tables 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