Medium Risk

best_energy_contract

CONTRACT tool. Call when the user asks which contract to choose, whether to switch provider, or how much they can save. Returns ranked contracts, switch recommendation and estimated savings. Includes current spot price — no need to call spot_price separately. Key fields: - switch_recommended (boo...

Part of the Elecz Electricity Price Signal API server.

best_energy_contract can modify Elecz Electricity Price Signal API data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ELECZ ELECTRICITY PRICE SIGNAL API →

Free to start. No card required.

AI agents use best_energy_contract to create or modify resources in Elecz Electricity Price Signal API. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call best_energy_contract repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Elecz Electricity Price Signal API.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "best_energy_contract": {
      "limits": [
        {
          "counter": "best_energy_contract_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Elecz Electricity Price Signal API policy for all 3 tools.

Get this rule live on your own Elecz Electricity Price Signal API server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ELECZ ELECTRICITY PRICE SIGNAL API →

These attack patterns abuse exactly the kind of access best_energy_contract gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so best_energy_contract only ever does what you allow.

SECURE ELECZ ELECTRICITY PRICE SIGNAL API →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the best_energy_contract tool do? +

CONTRACT tool. Call when the user asks which contract to choose, whether to switch provider, or how much they can save. Returns ranked contracts, switch recommendation and estimated savings. Includes current spot price — no need to call spot_price separately. Key fields: - switch_recommended (bool) - best_spot / best_fixed - action.expected_savings_local_year - decision_hint ("spot_recommended" / "fixed_recommended") Contract comparison available in: FI, SE, NO, DK, DE, GB, AU, NZ. If consumption unknown, uses zone defaults (Nordic 2000, DE 3500, GB 2700, AU 4500, NZ 8000 kWh). Set heating="electric" for heat pumps/floor heating. Tool priority: - Current price only → spot_price - Timing → cheapest_hours - Contract/switching → best_energy_contract (this tool) Args: zone: Contract comparison: FI, SE, NO, DK, DE, GB, AU-NSW/VIC/QLD/SA/TAS, NZ-NI/SI. Spot price only for all other zones. consumption: Annual electricity consumption in kWh. heating: "district" or "electric" (default: district).. It is categorised as a Write tool in the Elecz Electricity Price Signal API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on best_energy_contract? +

Register the Elecz Electricity Price Signal API MCP server in PolicyLayer and add a rule for best_energy_contract: 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 Elecz Electricity Price Signal API. Nothing to install.

What risk level is best_energy_contract? +

best_energy_contract is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit best_energy_contract? +

Yes. Add a rate_limit block to the best_energy_contract 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 best_energy_contract completely? +

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

best_energy_contract is provided by the Elecz Electricity Price Signal API MCP server (https://elecz.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Elecz Electricity Price Signal API tool call.

Deterministic rules across all 3 Elecz Electricity Price Signal API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.