world.country.search
Search country by name — population, area, capital, languages, currencies, timezones, flag, region, borders. 250+ countries. No auth, free (REST Countries)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/world.country.search.md
What world.country.search does on Apibase
AI agents call world.country.search 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 |
|---|---|---|---|
name | string | Yes | Country name to search (e.g. "United States", "Germany", "Japan") |
Parameters from the server's own tool schema.
Why world.country.search is rated Low
Retrieves public country metadata without side effects or mutations.
From the tool's definition Search country by name — population, area, capital, languages, currencies, timezones, flag, region, borders.
Attacks that exploit this kind of access
The rule that runs world.country.search 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 world.country.search, this is the rule to start with:
world.country.search 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 world.country.search call is checked against it from then on.
Questions about world.country.search
Search country by name — population, area, capital, languages, currencies, timezones, flag, region, borders. 250+ countries. No auth, free (REST Countries). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
world.country.search accepts 1 parameter: name. Required: name. 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 world.country.search: 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.
world.country.search 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 world.country.search 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 world.country.search. 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.
world.country.search 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