denmark-energidataservice.power.production_consumption
Get hourly Danish electricity production mix (central power, local power, offshore wind, onshore wind, hydro, solar) and gross consumption in MWh, per price zone (e.g. "DK1", "DK2"). Supports an optional date range (start_date/end_date); omit both to get the most recent hours. Data: Energinet, no...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/denmark-energidataservice.power.production-consumption.md
What denmark-energidataservice.power.production_consumption does on Apibase
AI agents call denmark-energidataservice.power.production_consumption 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 hourly production/consumption records to return (1-200, default 24) |
end_date | string | — | End of the time range, ISO 8601 (e.g. "2026-09-02"). Omit for the most recent data. |
price_area | string | — | Bidding/price zone to filter by, e.g. "DK1" (West Denmark), "DK2" (East Denmark), or a connected zone such as "DE", "NO2", "SE3". Omit to return all zones. |
start_date | string | — | Start of the time range, ISO 8601 (e.g. "2026-09-01" or "2026-09-01T00:00"). Omit for the most recent data. |
Parameters from the server's own tool schema.
Why denmark-energidataservice.power.production_consumption is rated Low
Tool retrieves historical energy data with no side effects, modifications, or external operations.
From the tool's definition Get hourly Danish electricity production mix and gross consumption in MWh
Attacks that exploit this kind of access
The rule that runs denmark-energidataservice.power.production_consumption 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 denmark-energidataservice.power.production_consumption, this is the rule to start with:
denmark-energidataservice.power.production_consumption 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 denmark-energidataservice.power.production_consumption call is checked against it from then on.
Questions about denmark-energidataservice.power.production_consumption
Get hourly Danish electricity production mix (central power, local power, offshore wind, onshore wind, hydro, solar) and gross consumption in MWh, per price zone (e.g. "DK1", "DK2"). Supports an optional date range (start_date/end_date); omit both to get the most recent hours. Data: Energinet, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
denmark-energidataservice.power.production_consumption accepts 4 parameters: limit, end_date, price_area, start_date. 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 denmark-energidataservice.power.production_consumption: 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.
denmark-energidataservice.power.production_consumption 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 denmark-energidataservice.power.production_consumption 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 denmark-energidataservice.power.production_consumption. 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.
denmark-energidataservice.power.production_consumption 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