unesco-data.reference.geounit_list
List the 462 country and world-region codes recognized by the UNESCO Institute for Statistics Data API, optionally filtered by name or level (NATIONAL/REGIONAL). Use this to find a valid geo_unit code for unesco-data.get_data. Example: query='Kenya'. Data: api.uis.unesco.org, no auth required, CC...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/unesco-data.reference.geounit-list.md
What unesco-data.reference.geounit_list does on Apibase
AI agents call unesco-data.reference.geounit_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 |
|---|---|---|---|
type | string | — | Filter to one geo unit level: NATIONAL (countries) or REGIONAL (world regions). |
query | string | — | Case-insensitive substring to match against country/region name, e.g. 'Kenya' or 'Africa'. |
Parameters from the server's own tool schema.
Why unesco-data.reference.geounit_list is rated Low
Tool retrieves UNESCO reference data without side effects or data modification capabilities.
From the tool's definition List country and world-region codes, optionally filtered by name or level
Attacks that exploit this kind of access
The rule that runs unesco-data.reference.geounit_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 unesco-data.reference.geounit_list, this is the rule to start with:
unesco-data.reference.geounit_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 unesco-data.reference.geounit_list call is checked against it from then on.
Questions about unesco-data.reference.geounit_list
List the 462 country and world-region codes recognized by the UNESCO Institute for Statistics Data API, optionally filtered by name or level (NATIONAL/REGIONAL). Use this to find a valid geo_unit code for unesco-data.get_data. Example: query='Kenya'. Data: api.uis.unesco.org, no auth required, CC BY-SA 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
unesco-data.reference.geounit_list accepts 2 parameters: type, 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 unesco-data.reference.geounit_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.
unesco-data.reference.geounit_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 unesco-data.reference.geounit_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 unesco-data.reference.geounit_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.
unesco-data.reference.geounit_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