eia_electricity_state
Monthly state-level electricity data from EIA. Filter by state (two-letter code or 'US' for national), sector (residential / commercial / industrial / transportation / all), and metric (price / sales / revenue / customers / generation). Default: US, all sectors, price.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/eia-electricity-state.md
What eia_electricity_state does on Livedatalink
AI agents call eia_electricity_state to retrieve information from Livedatalink 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 | — | Inclusive upper-bound period (ISO date or YYYY-MM). |
limit | number | — | Maximum rows to return (default 50, max 5000). |
start | string | — | Inclusive lower-bound period (ISO date or YYYY-MM depending on series cadence). |
state | string | — | Two-letter state code (e.g. 'TX', 'CA') or 'US' for national rollup. Default 'US'. |
metric | string | — | Metric: 'price', 'sales', 'revenue', 'customers', 'generation'. Default 'price'. |
sector | string | — | Sector: 'all', 'residential', 'commercial', 'industrial', 'transportation'. Default 'all'. |
Parameters from the server's own tool schema.
Why eia_electricity_state is rated Low
Even though eia_electricity_state only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs eia_electricity_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eia_electricity_state, this is the rule to start with:
eia_electricity_state 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 Livedatalink, apply this rule, and every eia_electricity_state call is checked against it from then on.
Questions about eia_electricity_state
Monthly state-level electricity data from EIA. Filter by state (two-letter code or 'US' for national), sector (residential / commercial / industrial / transportation / all), and metric (price / sales / revenue / customers / generation). Default: US, all sectors, price. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
eia_electricity_state accepts 6 parameters: end, limit, start, state, metric, sector. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for eia_electricity_state: 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 Livedatalink. Nothing to install.
eia_electricity_state 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 eia_electricity_state 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 eia_electricity_state. 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.
eia_electricity_state is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue