africa.data.indicator
Query a specific economic indicator time series for an African country. Supports 120+ metrics including GDP (gdp_usd), inflation rate (inflation_pct), GDP per capita (gdp_per_capita_usd), unemployment (unemployment_pct), trade balance (trade_balance_usd), foreign direct investment (fdi_inflows_us...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/africa.data.indicator.md
What africa.data.indicator does on Apibase
AI agents call africa.data.indicator 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 |
|---|---|---|---|
limit | integer | — | Maximum number of data points to return (1–100, default 20). |
end_year | integer | — | End year for historical range (e.g. 2024). Required when start_year is provided. |
metric_key | string | Yes | Economic indicator key (e.g. "gdp_usd" for GDP in USD, "inflation_pct" for CPI inflation rate, "gdp_per_capita_usd" for GDP per capita, "unemployment_pct" for u |
start_year | integer | — | Start year for historical range (e.g. 2015). Omit along with end_year to return the single latest observation. |
country_code | string | Yes | ISO 3166-1 alpha-2 country code (2-letter lowercase, e.g. "ng", "ke", "za", "eg", "gh"). |
Parameters from the server's own tool schema.
Why africa.data.indicator is rated Low
Tool retrieves historical economic data without modifying or executing external operations.
From the tool's definition Query economic indicator time series, returns annual data, no modification.
Attacks that exploit this kind of access
The rule that runs africa.data.indicator 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.data.indicator, this is the rule to start with:
africa.data.indicator 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.data.indicator call is checked against it from then on.
Questions about africa.data.indicator
Query a specific economic indicator time series for an African country. Supports 120+ metrics including GDP (gdp_usd), inflation rate (inflation_pct), GDP per capita (gdp_per_capita_usd), unemployment (unemployment_pct), trade balance (trade_balance_usd), foreign direct investment (fdi_inflows_usd), and more. Returns annual data sourced from World Bank, IMF, and UN. Omit start_year/end_year for latest value; supply both for a historical range (e.g. 2010–2024). Use africa.countries.signals to discover available metric_key values for a country. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
africa.data.indicator accepts 5 parameters: limit, end_year, metric_key, start_year, country_code. Required: metric_key, 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.data.indicator: 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.data.indicator 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.data.indicator 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.data.indicator. 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.data.indicator 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