List the statistical tables belonging to one INE operation. operationId may be the numeric Id (e.g. 25) or the operation code (e.g. "IPC", "EPA"). Each table has an Id used by series_in_table / table_data.
Part of the Ine Es server.
Free to start. No card required.
AI agents call tables_for_operation to retrieve information from Ine Es without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though tables_for_operation only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"tables_for_operation": {}
}
}See the full Ine Es policy for all 26 tools.
These attack patterns abuse exactly the kind of access tables_for_operation gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List the statistical tables belonging to one INE operation. operationId may be the numeric Id (e.g. 25) or the operation code (e.g. "IPC", "EPA"). Each table has an Id used by series_in_table / table_data.. It is categorised as a Read tool in the Ine Es MCP Server, which means it retrieves data without modifying state.
Register the Ine Es MCP server in PolicyLayer and add a rule for tables_for_operation: 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 Ine Es. Nothing to install.
tables_for_operation 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 tables_for_operation 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 tables_for_operation. 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.
tables_for_operation is provided by the Ine Es MCP server (https://gateway.pipeworx.io/ine-es/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Ine Es tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.