finance.eia.electricity
Retail electricity sales/price/revenue by US state and sector (residential, commercial, industrial). Frequency monthly/quarterly/annual. EIA public domain, 5K req/hr
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/finance.eia.electricity.md
What finance.eia.electricity does on Apibase
AI agents call finance.eia.electricity 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 |
|---|---|---|---|
end | string | — | Latest period in same format as `start`. |
start | string | — | Earliest period (e.g. "2020-01" monthly, "2020" annual). |
state | string | — | Optional 2-letter US state code (e.g. "CA", "TX", "NY"). If omitted, returns national + all states. |
length | integer | — | Number of recent observations to return (default 24, max 500). |
frequency | string | — | Time frequency (default "monthly"). |
Parameters from the server's own tool schema.
Why finance.eia.electricity is rated Low
Tool queries historical energy statistics with no side effects or financial transactions.
From the tool's definition Retrieves retail electricity sales, price, revenue data; public domain EIA.
Attacks that exploit this kind of access
The rule that runs finance.eia.electricity 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 finance.eia.electricity, this is the rule to start with:
finance.eia.electricity 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 finance.eia.electricity call is checked against it from then on.
Questions about finance.eia.electricity
Retail electricity sales/price/revenue by US state and sector (residential, commercial, industrial). Frequency monthly/quarterly/annual. EIA public domain, 5K req/hr. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
finance.eia.electricity accepts 5 parameters: end, start, state, length, frequency. 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 finance.eia.electricity: 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.
finance.eia.electricity 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 finance.eia.electricity 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 finance.eia.electricity. 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.
finance.eia.electricity 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