geoboundaries.boundary.list_countries
List every country's administrative boundary metadata at one level (ADM0 country outline by default, or ADM1-ADM5 for finer subdivisions where available): ISO3 code, name, admin unit count, continent/region, and geometry download URLs. Useful for discovering coverage before requesting a single co...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geoboundaries.boundary.list-countries.md
What geoboundaries.boundary.list_countries does on Apibase
AI agents call geoboundaries.boundary.list_countries 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 |
|---|---|---|---|
adm_level | string | — | Administrative boundary level: "ADM0" (country outline), "ADM1" (state/province/region), "ADM2" (county/district), "ADM3"-"ADM5" (finer subdivisions, only avail |
Parameters from the server's own tool schema.
Why geoboundaries.boundary.list_countries is rated Low
Tool retrieves public geospatial boundary metadata without modifying data or executing code.
From the tool's definition List every country's administrative boundary metadata
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs geoboundaries.boundary.list_countries 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 geoboundaries.boundary.list_countries, this is the rule to start with:
geoboundaries.boundary.list_countries 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 geoboundaries.boundary.list_countries call is checked against it from then on.
Questions about geoboundaries.boundary.list_countries
List every country's administrative boundary metadata at one level (ADM0 country outline by default, or ADM1-ADM5 for finer subdivisions where available): ISO3 code, name, admin unit count, continent/region, and geometry download URLs. Useful for discovering coverage before requesting a single country with geoboundaries.boundary.detail. Data: geoBoundaries (William & Mary geoLab), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
geoboundaries.boundary.list_countries accepts 1 parameter: adm_level. 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 geoboundaries.boundary.list_countries: 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.
geoboundaries.boundary.list_countries 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 geoboundaries.boundary.list_countries 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 geoboundaries.boundary.list_countries. 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.
geoboundaries.boundary.list_countries 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