geonames.country.info
Get structured metadata for any country or all countries from the GeoNames database. Returns country code (ISO-3166 alpha-2/alpha-3/numeric), capital, continent, official languages, population, area in km², currency code, postal code format/regex, geoname_id, and a bounding box (north/south/east/...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geonames.country.info.md
What geonames.country.info does on Apibase
AI agents call geonames.country.info 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 | — | ISO-3166 2-letter country code (e.g. "US", "DE", "JP"). Omit to retrieve all countries. |
language | string | — | ISO 639-1 language code for localized country names (e.g. "en", "fr", "es") |
Parameters from the server's own tool schema.
Why geonames.country.info is rated Low
Retrieves public GeoNames database metadata; no state changes or side effects.
From the tool's definition Get structured metadata for any country, returns country code, capital, continent, languages, population.
Attacks that exploit this kind of access
The rule that runs geonames.country.info 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 geonames.country.info, this is the rule to start with:
geonames.country.info 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 geonames.country.info call is checked against it from then on.
Questions about geonames.country.info
Get structured metadata for any country or all countries from the GeoNames database. Returns country code (ISO-3166 alpha-2/alpha-3/numeric), capital, continent, official languages, population, area in km², currency code, postal code format/regex, geoname_id, and a bounding box (north/south/east/west lat-lng). Omit country to retrieve all 250 countries in a single response. Supports localized country names via lang parameter. CC BY 4.0 open data, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
geonames.country.info accepts 2 parameters: country, language. 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 geonames.country.info: 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.
geonames.country.info 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 geonames.country.info 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 geonames.country.info. 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.
geonames.country.info 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