Browse or keyword-search ILOSTAT datasets (dataflows) from the International Labour Organization. Each result has an id (the dataflowId you pass to get_data / dataflow_structure) and an English name. ILO publishes ~1,200 datasets covering employment, unemployment, labour force participation, wage...
Risk signalsAccepts freeform code/query input (query)
Part of the Ilostat server.
Free to start. No card required.
AI agents call list_dataflows to retrieve information from Ilostat 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 list_dataflows 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": {
"list_dataflows": {}
}
}See the full Ilostat policy for all 23 tools.
These attack patterns abuse exactly the kind of access list_dataflows 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.
Browse or keyword-search ILOSTAT datasets (dataflows) from the International Labour Organization. Each result has an id (the dataflowId you pass to get_data / dataflow_structure) and an English name. ILO publishes ~1,200 datasets covering employment, unemployment, labour force participation, wages, hours worked, informality, working poverty, child labour, and occupational safety. Always pass query to filter unless you really want the whole list. Example: list_dataflows({ query: "unemployment rate" }) or list_dataflows({ query: "minimum wage" }).. It is categorised as a Read tool in the Ilostat MCP Server, which means it retrieves data without modifying state.
Register the Ilostat MCP server in PolicyLayer and add a rule for list_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 Ilostat. Nothing to install.
list_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 list_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 list_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.
list_dataflows is provided by the Ilostat MCP server (https://gateway.pipeworx.io/ilostat/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Ilostat 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.