geoboundaries.boundary.available_levels
Check which administrative levels (ADM0 through ADM5) exist for a given country, with the local admin name and unit count at each available level (e.g. Kenya has ADM0-ADM2 only; France has ADM0-ADM4). Call this before geoboundaries.boundary.detail to avoid requesting a level that does not exist f...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geoboundaries.boundary.available-levels.md
What geoboundaries.boundary.available_levels does on Apibase
AI agents call geoboundaries.boundary.available_levels 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 |
|---|---|---|---|
country | string | Yes | ISO 3166-1 alpha-3 country code, uppercase (e.g. "USA", "KEN", "FRA"). ISO2 codes and country names are not accepted by the upstream API. |
Parameters from the server's own tool schema.
Why geoboundaries.boundary.available_levels is rated Low
Queries administrative boundary data without modification, side effects, or access restrictions.
From the tool's definition Check which administrative levels exist, no auth required
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs geoboundaries.boundary.available_levels 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.available_levels, this is the rule to start with:
geoboundaries.boundary.available_levels 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.available_levels call is checked against it from then on.
Questions about geoboundaries.boundary.available_levels
Check which administrative levels (ADM0 through ADM5) exist for a given country, with the local admin name and unit count at each available level (e.g. Kenya has ADM0-ADM2 only; France has ADM0-ADM4). Call this before geoboundaries.boundary.detail to avoid requesting a level that does not exist for that country. 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.available_levels accepts 1 parameter: country. Required: country. 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.available_levels: 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.available_levels 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.available_levels 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.available_levels. 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.available_levels 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