ine-chile.reference.dataflows
Search or list Chilean SIMEL (labour-market information system) dataflows — the ~204 official indicator series covering employment, unemployment, wages, pensions, and gender gaps, split by demographic and geographic breakdowns. Filter by name/id with query, or omit to list all. Use the returned d...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ine-chile.reference.dataflows.md
What ine-chile.reference.dataflows does on Apibase
AI agents call ine-chile.reference.dataflows 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 |
|---|---|---|---|
query | string | — | Filter dataflows by name or id substring, case-insensitive (e.g. "desocup" for unemployment, "sexo" for gender-split indicators). Omit to list all ~204 availabl |
Parameters from the server's own tool schema.
Why ine-chile.reference.dataflows is rated Low
Tool queries and lists publicly available labor market metadata without side effects or data modification.
From the tool's definition Search or list Chilean SIMEL dataflows, labour-market information system, no auth required.
Attacks that exploit this kind of access
The rule that runs ine-chile.reference.dataflows 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-chile.reference.dataflows, this is the rule to start with:
ine-chile.reference.dataflows 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-chile.reference.dataflows call is checked against it from then on.
Questions about ine-chile.reference.dataflows
Search or list Chilean SIMEL (labour-market information system) dataflows — the ~204 official indicator series covering employment, unemployment, wages, pensions, and gender gaps, split by demographic and geographic breakdowns. Filter by name/id with query, or omit to list all. Use the returned dataflow_id with ine-chile.structure and ine-chile.data. Data: sdmx.ine.gob.cl (INE Chile SDMX 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-chile.reference.dataflows accepts 1 parameter: query. 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-chile.reference.dataflows: 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-chile.reference.dataflows 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-chile.reference.dataflows 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-chile.reference.dataflows. 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-chile.reference.dataflows 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