getOilSpotPrice
Returns the U.S. EIA's official daily spot price for the benchmark's physical hub, on every plan. The EIA publishes weekly, so the date field says which trading day the price is for. Currency and unit conversion are premium features; the types batch parameter is available to Business, Professiona...
This record as markdown: /tools/com-api-ninjas-mcp/getoilspotprice.md
What getOilSpotPrice does on API Ninjas
AI agents call getOilSpotPrice to retrieve information from API Ninjas 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 |
|---|---|---|---|
type | string | — | The benchmark to return. Defaults to wti. crude_oil, brent_crude_oil, gasoline_rbob, and heating_oil are also accepted as aliases. |
unit | string | — | Target unit to convert the price into. Must match the benchmark's dimension: crude oil, gasoline, and diesel (volume) accept barrel, gallon, liter, or cubic_met |
types | string | — | Comma-separated list of benchmarks for a batch request. Available to Business, Professional, and Enterprise subscribers, or any annual plan. |
currency | string | — | ISO 4217 currency code to convert the price into (e.g., EUR, GBP, INR). Premium feature. |
Parameters from the server's own tool schema.
Why getOilSpotPrice is rated Low
Even though getOilSpotPrice 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs getOilSpotPrice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getOilSpotPrice, this is the rule to start with:
getOilSpotPrice 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 API Ninjas, apply this rule, and every getOilSpotPrice call is checked against it from then on.
Questions about getOilSpotPrice
Returns the U.S. EIA's official daily spot price for the benchmark's physical hub, on every plan. The EIA publishes weekly, so the date field says which trading day the price is for. Currency and unit conversion are premium features; the types batch parameter is available to Business, Professional, and Enterprise subscribers, or any annual plan. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getOilSpotPrice accepts 4 parameters: type, unit, types, currency. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getOilSpotPrice: 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 API Ninjas. Nothing to install.
getOilSpotPrice 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 getOilSpotPrice 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 getOilSpotPrice. 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.
getOilSpotPrice is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue