AI agents call get_current_price to retrieve information from Elpriser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation—fetching the current electricity price for a specified price zone. There are no side effects, no data modification, no code execution, and no financial transactions. The blast radius of misuse is minimal; an agent could only retrieve price information that is already public. This is a straightforward Read operation.
From the tool's definition Tool name 'get_current_price' and description indicate it 'Get[s] the current Danish electricity price (this hour) for a price zone'. This is a query operation that retrieves pricing data without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get the current Danish electricity price (this hour) for a price zone. Use for. It is categorised as a Read tool in the Elpriser MCP Server, which means it retrieves data without modifying state.
Register the Elpriser MCP server in PolicyLayer and add a rule for get_current_price: 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 Elpriser. Nothing to install.
get_current_price 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 get_current_price 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 get_current_price. 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.
get_current_price is provided by the Elpriser MCP server (x2q/elpriser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →