econ.commodity
Latest benchmark commodity price + % change. Pass commodity (wti, brent, natural-gas, gasoline, diesel, heating-oil, propane, copper, aluminum, corn, wheat, sugar) or omit for all. Each names the FRED series + unit. Source: EIA/IMF via FRED.
This record as markdown: /tools/io-github-2s-io-mcp/econ.commodity.md
What econ.commodity does on Mcp
AI agents call econ.commodity to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why econ.commodity is rated Low
This tool queries and returns commodity price data. It has no side effects, does not modify any data, does not execute code or commands, and does not perform financial transactions. The fact that the MCP server is settlement-based (pay-per-call in USDC) is a billing model for tool access, not a property of this specific tool. Reading commodity prices is a classic Read category operation.
From the tool's definition Tool retrieves 'Latest benchmark commodity price + % change' from external data sources (EIA/IMF via FRED). It is a query/fetch operation with no parameters that modify state or execute code.
Attacks that exploit this kind of access
The rule that runs econ.commodity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For econ.commodity, this is the rule to start with:
econ.commodity 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 Mcp, apply this rule, and every econ.commodity call is checked against it from then on.
Questions about econ.commodity
Latest benchmark commodity price + % change. Pass commodity (wti, brent, natural-gas, gasoline, diesel, heating-oil, propane, copper, aluminum, corn, wheat, sugar) or omit for all. Each names the FRED series + unit. Source: EIA/IMF via FRED. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for econ.commodity: 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 Mcp. Nothing to install.
econ.commodity 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 econ.commodity 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 econ.commodity. 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.
econ.commodity is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue