africa.countries.signals
Get a live macroeconomic snapshot for an African country. Returns 20–60 indicators across economy (GDP, inflation, trade), climate (precipitation, air quality), health (life expectancy, access to services), and demographic signals. Sources: World Bank WDI, IMF, UN, NASA POWER. Use country_code fr...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/africa.countries.signals.md
What africa.countries.signals does on Apibase
AI agents call africa.countries.signals 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_code | string | Yes | ISO 3166-1 alpha-2 country code (2-letter lowercase, e.g. "ng" for Nigeria, "ke" for Kenya, "za" for South Africa, "eg" for Egypt, "gh" for Ghana). |
Parameters from the server's own tool schema.
Why africa.countries.signals is rated Low
Retrieves and aggregates public macroeconomic data without modification or execution capabilities.
From the tool's definition Get a live macroeconomic snapshot, returns indicators across economy, climate, health, demographic signals.
Attacks that exploit this kind of access
The rule that runs africa.countries.signals 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 africa.countries.signals, this is the rule to start with:
africa.countries.signals 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 africa.countries.signals call is checked against it from then on.
Questions about africa.countries.signals
Get a live macroeconomic snapshot for an African country. Returns 20–60 indicators across economy (GDP, inflation, trade), climate (precipitation, air quality), health (life expectancy, access to services), and demographic signals. Sources: World Bank WDI, IMF, UN, NASA POWER. Use country_code from africa.countries.list. Ideal for rapid country assessment and investment screening across 54 African nations. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
africa.countries.signals accepts 1 parameter: country_code. Required: country_code. 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 africa.countries.signals: 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.
africa.countries.signals 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 africa.countries.signals 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 africa.countries.signals. 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.
africa.countries.signals 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