eia_oil_supply
Weekly US crude oil supply data from EIA. Metrics: 'production' (US field production), 'imports' (weekly oil imports), 'stocks' (commercial crude stocks), 'refinery_inputs' (gross refinery inputs). Filter by PADD region. Default: national production.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/eia-oil-supply.md
What eia_oil_supply does on Livedatalink
AI agents call eia_oil_supply 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). |
metric | string | — | Metric: 'production', 'imports', 'stocks', 'refinery_inputs'. Default 'production'. |
region | string | — | PADD region or 'national'. Examples: 'national', 'PADD1', 'PADD3'. Default 'national'. |
Parameters from the server's own tool schema.
Why eia_oil_supply is rated Low
Even though eia_oil_supply 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_oil_supply 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_oil_supply, this is the rule to start with:
eia_oil_supply 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_oil_supply call is checked against it from then on.
Questions about eia_oil_supply
Weekly US crude oil supply data from EIA. Metrics: 'production' (US field production), 'imports' (weekly oil imports), 'stocks' (commercial crude stocks), 'refinery_inputs' (gross refinery inputs). Filter by PADD region. Default: national production. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
eia_oil_supply accepts 5 parameters: end, limit, start, metric, region. 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_oil_supply: 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_oil_supply 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_oil_supply 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_oil_supply. 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_oil_supply 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