Time-series of electricity unit rates for a specific tariff — for Agile this is the half-hourly wholesale-tracked pricing. Returns {count, results:[{value_exc_vat, value_inc_vat, valid_from, valid_to, payment_method}]} in p/kWh, newest first. Set kind="standing_charges" for the p/day standing cha...
Part of the Octopus Energy server.
Free to start. No card required.
AI agents use tariff_unit_rates to create or modify resources in Octopus Energy. 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 tariff_unit_rates 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 Octopus Energy.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"tariff_unit_rates": {
"limits": [
{
"counter": "tariff_unit_rates_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Octopus Energy policy for all 24 tools.
These attack patterns abuse exactly the kind of access tariff_unit_rates gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Time-series of electricity unit rates for a specific tariff — for Agile this is the half-hourly wholesale-tracked pricing. Returns {count, results:[{value_exc_vat, value_inc_vat, valid_from, valid_to, payment_method}]} in p/kWh, newest first. Set kind="standing_charges" for the p/day standing charge instead. Defaults to the most recent rates; pass period_from/period_to to bound a window.. It is categorised as a Write tool in the Octopus Energy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Octopus Energy MCP server in PolicyLayer and add a rule for tariff_unit_rates: 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 Octopus Energy. Nothing to install.
tariff_unit_rates is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tariff_unit_rates 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 tariff_unit_rates. 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.
tariff_unit_rates is provided by the Octopus Energy MCP server (https://gateway.pipeworx.io/octopus-energy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Octopus Energy 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.