unsdg.indicators.list
List UN SDG monitoring indicators with their series codes, tier classifications (Tier I = established methodology, Tier II = methodology in development, Tier III = no agreed methodology), and associated data series codes. Optionally filter by goal (1–17) or target (e.g. "3.3"). Series codes (e.g....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/unsdg.indicators.list.md
What unsdg.indicators.list does on Apibase
AI agents call unsdg.indicators.list 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 |
|---|---|---|---|
goal | string | — | Filter indicators by SDG goal number (e.g. "1", "3", "13"). If omitted, all 231 indicators across all 17 goals are returned. |
target | string | — | Filter indicators by target code (e.g. "1.1", "3.3", "13.2"). Requires goal to be set for best results. |
Parameters from the server's own tool schema.
Why unsdg.indicators.list is rated Low
Lists metadata about UN SDG indicators without modifying data or enabling further access without separate queries.
From the tool's definition List UN SDG monitoring indicators with series codes, filter by goal or target.
Attacks that exploit this kind of access
The rule that runs unsdg.indicators.list 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 unsdg.indicators.list, this is the rule to start with:
unsdg.indicators.list 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 unsdg.indicators.list call is checked against it from then on.
Questions about unsdg.indicators.list
List UN SDG monitoring indicators with their series codes, tier classifications (Tier I = established methodology, Tier II = methodology in development, Tier III = no agreed methodology), and associated data series codes. Optionally filter by goal (1–17) or target (e.g. "3.3"). Series codes (e.g. "SI_POV_DAY1", "SH_STA_MORT") are the inputs to unsdg.data.query for fetching actual country-level time series data. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
unsdg.indicators.list accepts 2 parameters: goal, target. 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 unsdg.indicators.list: 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.
unsdg.indicators.list 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 unsdg.indicators.list 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 unsdg.indicators.list. 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.
unsdg.indicators.list 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