New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

irena.energy.generation_country

Query electricity generation (GWh) by energy technology for any country from the IRENA IRENASTAT database. Covers 226 countries and territories, 21 technologies including Total renewable, Solar PV, Onshore and Offshore wind, Renewable hydropower, Bioenergy subcategories, Geothermal, Marine energy...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 51 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/irena.energy.generation-country.md

What irena.energy.generation_country does on Apibase

AI agents call irena.energy.generation_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.

ParameterTypeRequiredDescription
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–2024, must be ≥ year_from). Default: 2024.
year_from integer — Start year (inclusive, 2000–2024). Default: 2020.
technology string — Energy technology to query. Default: "Total renewable". Options: Total renewable, Solar photovoltaic, Onshore wind energy, Offshore wind energy, Renewable hydro
grid_connection string — Grid connection type. Default: "OnGrid".

Parameters from the server's own tool schema.

Why irena.energy.generation_country is rated Low

Tool retrieves historical energy statistics from public database with no side effects or modifications.

From the tool's definition Query electricity generation (GWh) by energy technology for any country

Questions about irena.energy.generation_country

What does the irena.energy.generation_country tool do? +

Query electricity generation (GWh) by energy technology for any country from the IRENA IRENASTAT database. Covers 226 countries and territories, 21 technologies including Total renewable, Solar PV, Onshore and Offshore wind, Renewable hydropower, Bioenergy subcategories, Geothermal, Marine energy, and Total non-renewable. On-grid, off-grid, or combined. Annual data from 2000 to 2024. Essential for energy transition analysis, NDC tracking, and climate policy research. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does irena.energy.generation_country accept? +

irena.energy.generation_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.

How do I enforce a policy on irena.energy.generation_country? +

Register the Apibase MCP server in PolicyLayer and add a rule for irena.energy.generation_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.

What risk level is irena.energy.generation_country? +

irena.energy.generation_country is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit irena.energy.generation_country? +

Yes. Add a rate_limit block to the irena.energy.generation_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.

How do I block irena.energy.generation_country completely? +

Set action: deny in the PolicyLayer policy for irena.energy.generation_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.

What MCP server provides irena.energy.generation_country? +

irena.energy.generation_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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.