wto.trade.data
Retrieve official World Trade Organization time-series data for trade and tariff indicators by reporting economy and year. Covers 58 indicators across three domains: tariff profiles (MFN applied/bound tariff averages, HS-level ad valorem duties by product), merchandise trade values (exports and i...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wto.trade.data.md
What wto.trade.data does on Apibase
AI agents call wto.trade.data to retrieve information from Apibase 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 |
|---|---|---|---|
years | string | — | Comma-separated year(s) or year-ranges to retrieve (e.g. "2022", "2020,2021,2022", "2015-2022"). Omit to get all available years for the indicator. Most tariff/ |
max_rows | integer | — | Maximum number of data rows to return (1–500, default 100). Lower values are faster; raise for multi-year/multi-country queries. |
partner_codes | string | — | Comma-separated partner economy code(s) for bilateral trade data. Only applicable to indicators that have partner dimension (bilateral trade flows). Use "000" f |
reporter_codes | string | Yes | Comma-separated WTO reporter economy code(s). Use the 3-digit numeric codes from wto.trade.reporters — e.g. "840" for USA, "276" for Germany, "156" for China, " |
indicator_codes | string | Yes | Comma-separated WTO indicator code(s) to retrieve data for. Examples: "TP_A_0010" (MFN applied tariff, all products), "ITS_MTV_AX" (merchandise exports by produ |
Parameters from the server's own tool schema.
Why wto.trade.data is rated Low
Tool retrieves and queries public WTO trade data without modifying, executing code, or financial operations.
From the tool's definition Retrieve official World Trade Organization time-series data for trade and tariff indicators
Attacks that exploit this kind of access
The rule that runs wto.trade.data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wto.trade.data, this is the rule to start with:
wto.trade.data 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 Apibase, apply this rule, and every wto.trade.data call is checked against it from then on.
Questions about wto.trade.data
Retrieve official World Trade Organization time-series data for trade and tariff indicators by reporting economy and year. Covers 58 indicators across three domains: tariff profiles (MFN applied/bound tariff averages, HS-level ad valorem duties by product), merchandise trade values (exports and imports by product group, quarterly and monthly), and commercial services trade (exports and imports by sector and partner). Returns structured data rows with indicator code, reporting economy, partner economy (for bilateral flows), product/sector classification, year, value, and unit. Example queries: US MFN applied tariff in 2022 (indicator TP_A_0010, reporter 840), China merchandise exports 2018-2022 (ITS_MTV_AX, reporter 156), EU commercial services exports (ITS_CS_AX6, reporter 097). Use wto.trade.indicators to discover indicator codes with their categories, units, and year ranges. Use wto.trade.reporters to look up 3-digit economy codes. Data is updated annually/quarterly by WTO Statistics Division. Free tier: 10 req/s. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wto.trade.data accepts 5 parameters: years, max_rows, partner_codes, reporter_codes, indicator_codes. Required: reporter_codes, indicator_codes. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for wto.trade.data: 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 Apibase. Nothing to install.
wto.trade.data 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 wto.trade.data 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 wto.trade.data. 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.
wto.trade.data is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue