trade.commodity-resolve
Cross-walk a traded-good code across HS ↔ HTS ↔ Schedule B ↔ NAICS (+ SITC) via the shared HS6 (Census concordances).
This record as markdown: /tools/io-github-2s-io-mcp/trade.commodity-resolve.md
What trade.commodity-resolve does on Mcp
AI agents call trade.commodity-resolve 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 trade.commodity-resolve is rated Low
This tool performs a lookup/mapping of commodity classification codes across different trade nomenclature systems (HS, HTS, Schedule B, NAICS, SITC). It is a read/query operation that retrieves concordance data.
From the tool's definition Cross-walk a traded-good code across HS ↔ HTS ↔ Schedule B ↔ NAICS (+ SITC) via the shared HS6 (Census concordances)
Attacks that exploit this kind of access
The rule that runs trade.commodity-resolve 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 trade.commodity-resolve, this is the rule to start with:
trade.commodity-resolve 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 trade.commodity-resolve call is checked against it from then on.
Questions about trade.commodity-resolve
Cross-walk a traded-good code across HS ↔ HTS ↔ Schedule B ↔ NAICS (+ SITC) via the shared HS6 (Census concordances). 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 trade.commodity-resolve: 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.
trade.commodity-resolve 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 trade.commodity-resolve 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 trade.commodity-resolve. 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.
trade.commodity-resolve 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