carbonintensity.energy.regional
Get carbon intensity and generation mix for UK electricity distribution regions. Returns data for all 14–18 UK DNO (Distribution Network Operator) regions, or a single region by region ID (1=North Scotland, 2=South Scotland, 3=North West England, 4=North East England, 5=Yorkshire, 6=North Wales &...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/carbonintensity.energy.regional.md
What carbonintensity.energy.regional does on Apibase
AI agents call carbonintensity.energy.regional 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 |
|---|---|---|---|
region_id | integer | — | UK DNO region ID (1–14 for primary regions, up to 18 for all). Omit to return all regions. 1=North Scotland, 2=South Scotland, 3=North West England, 4=North Eas |
Parameters from the server's own tool schema.
Why carbonintensity.energy.regional is rated Low
Retrieves publicly available UK energy carbon data without side effects or resource access.
From the tool's definition Get carbon intensity and generation mix for UK electricity distribution regions. Returns data.
Attacks that exploit this kind of access
The rule that runs carbonintensity.energy.regional 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 carbonintensity.energy.regional, this is the rule to start with:
carbonintensity.energy.regional 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 carbonintensity.energy.regional call is checked against it from then on.
Questions about carbonintensity.energy.regional
Get carbon intensity and generation mix for UK electricity distribution regions. Returns data for all 14–18 UK DNO (Distribution Network Operator) regions, or a single region by region ID (1=North Scotland, 2=South Scotland, 3=North West England, 4=North East England, 5=Yorkshire, 6=North Wales & Mersey, 7=South Wales, 8=West Midlands, 9=East Midlands, 10=East England, 11=South West England, 12=South England, 13=London, 14=South East England). Each region includes forecast intensity in gCO2/kWh, qualitative index, and generation mix percentages. Useful for location-aware carbon-minimising energy decisions. CC BY 4.0, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
carbonintensity.energy.regional accepts 1 parameter: region_id. 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 carbonintensity.energy.regional: 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.
carbonintensity.energy.regional 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 carbonintensity.energy.regional 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 carbonintensity.energy.regional. 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.
carbonintensity.energy.regional 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