worldbank_compare
Compare the most recent value of a World Bank indicator across multiple countries (up to 6). Provide a comma-separated list of country codes or names.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/worldbank-compare.md
What worldbank_compare does on Livedatalink
AI agents call worldbank_compare to retrieve information from Livedatalink 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 |
|---|---|---|---|
countries | string | Yes | Comma-separated country codes/names, e.g. 'US,CN,DE,JP'. |
indicator | string | — | Indicator name (one of: gdp, gdp_per_capita, gdp_growth, inflation, population, unemployment, life_expectancy, exports, imports, gni_per_capita, poverty_rate, i |
Parameters from the server's own tool schema.
Why worldbank_compare is rated Low
This tool performs a read-only retrieval and comparison of publicly available World Bank indicator data. It queries existing data across multiple countries but does not modify, create, execute external operations, delete, or move money. The blast radius of misuse is minimal—worst case an agent queries unexpected country combinations, which merely returns data harmlessly.
From the tool's definition Tool description states it 'Compare[s] the most recent value of a World Bank indicator across multiple countries' — a query operation that retrieves and displays data with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
The rule that runs worldbank_compare safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For worldbank_compare, this is the rule to start with:
worldbank_compare 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 Livedatalink, apply this rule, and every worldbank_compare call is checked against it from then on.
Questions about worldbank_compare
Compare the most recent value of a World Bank indicator across multiple countries (up to 6). Provide a comma-separated list of country codes or names. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
worldbank_compare accepts 2 parameters: countries, indicator. Required: countries. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for worldbank_compare: 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 Livedatalink. Nothing to install.
worldbank_compare 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 worldbank_compare 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 worldbank_compare. 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.
worldbank_compare is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue