irena.energy.capacity_country
Query renewable and non-renewable electricity installed capacity (MW) for any country from the IRENA IRENASTAT database. Covers 226 countries and territories, 26 energy technologies (Total renewable energy, Solar photovoltaic, Wind, Hydropower, Bioenergy, Geothermal, etc.), on-grid and off-grid, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/irena.energy.capacity-country.md
What irena.energy.capacity_country does on Apibase
AI agents call irena.energy.capacity_country 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 | Yes | ISO 3166-1 alpha-3 country code (e.g. USA, DEU, CHN, IND, BRA). Must be exactly 3 letters. |
year_to | integer | — | End year (inclusive, 2000–2025, must be ≥ year_from). Default: 2025. |
year_from | integer | — | Start year (inclusive, 2000–2025). Default: 2020. |
technology | string | — | Energy technology to query. Default: "Total renewable energy". Renewable options: Total renewable energy, Solar energy, Solar photovoltaic, Wind energy, Onshore |
grid_connection | string | — | Grid connection type. Default: "OnGrid". |
Parameters from the server's own tool schema.
Why irena.energy.capacity_country is rated Low
Retrieves historical energy statistics from public databases with no side effects.
From the tool's definition Query renewable and non-renewable electricity installed capacity (MW) for any country
Attacks that exploit this kind of access
The rule that runs irena.energy.capacity_country 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 irena.energy.capacity_country, this is the rule to start with:
irena.energy.capacity_country 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 irena.energy.capacity_country call is checked against it from then on.
Questions about irena.energy.capacity_country
Query renewable and non-renewable electricity installed capacity (MW) for any country from the IRENA IRENASTAT database. Covers 226 countries and territories, 26 energy technologies (Total renewable energy, Solar photovoltaic, Wind, Hydropower, Bioenergy, Geothermal, etc.), on-grid and off-grid, from 2000 to 2025. Returns a time-series of MW values per year. Official IRENA data — the authoritative global source for renewable energy statistics used by the IPCC, IEA, and UN agencies. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
irena.energy.capacity_country accepts 5 parameters: country, year_to, year_from, technology, grid_connection. Required: country. 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 irena.energy.capacity_country: 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.
irena.energy.capacity_country 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 irena.energy.capacity_country 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 irena.energy.capacity_country. 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.
irena.energy.capacity_country 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