denmark-energidataservice.power.spot_prices

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/denmark-energidataservice.power.spot-prices.md

WHAT IT DOES

What denmark-energidataservice.power.spot_prices does on Apibase

AI agents call denmark-energidataservice.power.spot_prices 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 price points 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.

RISK

Why denmark-energidataservice.power.spot_prices is rated Low

Tool retrieves historical and current electricity pricing data without modifying, deleting, or executing operations.

From the tool's definition Get hourly day-ahead electricity spot prices, returns price data, no auth required

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs denmark-energidataservice.power.spot_prices 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.spot_prices, this is the rule to start with:

denmark-energidataservice.power.spot_prices Allowed

denmark-energidataservice.power.spot_prices is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "denmark-energidataservice.power.spot_prices": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every denmark-energidataservice.power.spot_prices call is checked against it from then on.

FAQ

Questions about denmark-energidataservice.power.spot_prices

What does the denmark-energidataservice.power.spot_prices tool do? +

Get hourly day-ahead electricity spot prices for a Nordic/European bidding zone (e.g. "DK1", "DK2", or connected zones like "DE", "NO2", "SE3"). Returns each hour's price in both DKK/MWh and EUR/MWh. Supports an optional date range (start_date/end_date); omit both to get the most recent hours. Data: Energinet (Danish TSO), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does denmark-energidataservice.power.spot_prices accept? +

denmark-energidataservice.power.spot_prices 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.

How do I enforce a policy on denmark-energidataservice.power.spot_prices? +

Register the Apibase MCP server in PolicyLayer and add a rule for denmark-energidataservice.power.spot_prices: 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 denmark-energidataservice.power.spot_prices? +

denmark-energidataservice.power.spot_prices is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit denmark-energidataservice.power.spot_prices? +

Yes. Add a rate_limit block to the denmark-energidataservice.power.spot_prices 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 denmark-energidataservice.power.spot_prices completely? +

Set action: deny in the PolicyLayer policy for denmark-energidataservice.power.spot_prices. 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 denmark-energidataservice.power.spot_prices? +

denmark-energidataservice.power.spot_prices 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →