Get spot prices, 24h/7d trend, and supply/demand signals for physical commodities: gold, silver, crude oil, wheat, corn, copper, and natural gas. Use this tool when: - An agent needs commodity prices for macro analysis or trade decisions - A portfolio agent wants to assess inflationary pressures ...
AI agents call get_commodities to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it queries and retrieves commodity market data without side effects. Severity is medium (not low) because the tool sits on a pay-per-call financial data platform (USDC on Base Mainnet) and the data returned (prices, trends, supply/demand signals) directly informs trading and investment decisions.
From the tool's definition Tool retrieves spot prices, trend data (24h/7d changes, 52w highs/lows), and supply/demand signals for commodities. Returns data only: spot_price, currency, 24h_change_pct, 7d_change_pct, 52w_high, 52w_low, supply_signal, demand_signal.
Attacks that exploit this kind of access
Get spot prices, 24h/7d trend, and supply/demand signals for physical commodities: gold, silver, crude oil, wheat, corn, copper, and natural gas. Use this tool when: - An agent needs commodity prices for macro analysis or trade decisions - A portfolio agent wants to assess inflationary pressures via commodity trends - A trading agent is looking for correlated assets (e.g. gold as USD hedge) - You need supply/demand context for commodity price movements Returns per commodity: spot_price, currency, 24h_change_pct, 7d_change_pct, 52w_high, 52w_low, supply_signal (TIGHT/NORMAL/SURPLUS), demand_signal, key_drivers. Example: getCommodities({ commodities:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_commodities: 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 Omni Service Node. Nothing to install.
get_commodities 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 get_commodities 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 get_commodities. 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.
get_commodities is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_commodities is one line of Omni Service Node's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →