geoboundaries.boundary.detail

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geoboundaries.boundary.detail.md

WHAT IT DOES

What geoboundaries.boundary.detail does on Apibase

AI agents call geoboundaries.boundary.detail 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.
`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.

RISK

Why geoboundaries.boundary.detail is rated Low

Tool retrieves boundary metadata and file URLs; no side effects, no data modification, no execution.

From the tool's definition Get metadata, download URLs, no geometry embedded, no auth required

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs geoboundaries.boundary.detail 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.detail, this is the rule to start with:

geoboundaries.boundary.detail Allowed

geoboundaries.boundary.detail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "geoboundaries.boundary.detail": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every geoboundaries.boundary.detail call is checked against it from then on.

FAQ

Questions about geoboundaries.boundary.detail

What does the geoboundaries.boundary.detail tool do? +

Get metadata for one country's administrative boundary at a given level: official name, admin unit count, area/perimeter stats, source, license, and download URLs for the full GeoJSON, simplified GeoJSON, TopoJSON, and a preview PNG. Levels: ADM0 (country outline), ADM1 (state/province), ADM2 (county/district), ADM3-ADM5 (finer, country-dependent). Geometry is NOT embedded in the response (files can exceed 10MB) — fetch the returned URL directly for the shapes. 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.

What parameters does geoboundaries.boundary.detail accept? +

geoboundaries.boundary.detail accepts 2 parameters: country, adm_level. Required: country. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on geoboundaries.boundary.detail? +

Register the Apibase MCP server in PolicyLayer and add a rule for geoboundaries.boundary.detail: 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.

What risk level is geoboundaries.boundary.detail? +

geoboundaries.boundary.detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit geoboundaries.boundary.detail? +

Yes. Add a rate_limit block to the geoboundaries.boundary.detail 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.

How do I block geoboundaries.boundary.detail completely? +

Set action: deny in the PolicyLayer policy for geoboundaries.boundary.detail. 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.

What MCP server provides geoboundaries.boundary.detail? +

geoboundaries.boundary.detail 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →