Get the structure (Data Structure Definition) of one ILOSTAT dataset: its ordered dimensions and, for each, the valid codes. Use this to learn how to build the dot-separated SDMX key for get_data. The key positions correspond to the dimensions in order; an empty position is a wildcard. Common dim...
Part of the Ilostat server.
Free to start. No card required.
AI agents invoke dataflow_structure to trigger processes or run actions in Ilostat. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
dataflow_structure can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"dataflow_structure": {
"limits": [
{
"counter": "dataflow_structure_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Ilostat policy for all 23 tools.
These attack patterns abuse exactly the kind of access dataflow_structure gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Get the structure (Data Structure Definition) of one ILOSTAT dataset: its ordered dimensions and, for each, the valid codes. Use this to learn how to build the dot-separated SDMX key for get_data. The key positions correspond to the dimensions in order; an empty position is a wildcard. Common dimensions are REF_AREA (ISO3 country code, e.g. "USA", "FRA"), FREQ (A=annual, Q=quarterly, M=monthly), SEX, AGE, and MEASURE. Always call this before get_data. Example: dataflow_structure({ dataflow_id: "DF_SDG_0852_SEX_AGE_RT" }).. It is categorised as a Execute tool in the Ilostat MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ilostat MCP server in PolicyLayer and add a rule for dataflow_structure: 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.
dataflow_structure is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dataflow_structure 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 dataflow_structure. 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.
dataflow_structure 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.