comtrade.trade.metadata
Retrieve methodological metadata for a UN Comtrade dataset: the reporting currency, USD conversion factors applied (import/export), trade system used (General vs Special trade), import/export valuation method (CIF vs FOB), partner country attribution rules, and publication notes. Essential for un...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/comtrade.trade.metadata.md
What comtrade.trade.metadata does on Apibase
AI agents call comtrade.trade.metadata 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 |
|---|---|---|---|
period | string | Yes | Reference period. Annual: 4-digit year (e.g. "2022"). Monthly: YYYYMM (e.g. "202209"). Returns currency conversion factors, trade system, valuation notes for th |
freq_code | string | — | Frequency. A=Annual (default), M=Monthly. |
type_code | string | — | Data type. C=Commodities (default), S=Services. |
show_history | boolean | — | Include historical revisions in the metadata response. Default false (returns only the latest version). |
reporter_code | integer | Yes | UN numeric code for the reporting country. Example: 276=Germany, 840=USA, 156=China. Use comtrade.reporters to look up codes. |
classification | string | — | Classification system. HS=Harmonized System (default). |
Parameters from the server's own tool schema.
Why comtrade.trade.metadata is rated Low
Tool retrieves static metadata about trade reporting methodology with no side effects or data modification capabilities.
From the tool's definition Retrieve methodological metadata for a UN Comtrade dataset
Attacks that exploit this kind of access
The rule that runs comtrade.trade.metadata 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 comtrade.trade.metadata, this is the rule to start with:
comtrade.trade.metadata 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 comtrade.trade.metadata call is checked against it from then on.
Questions about comtrade.trade.metadata
Retrieve methodological metadata for a UN Comtrade dataset: the reporting currency, USD conversion factors applied (import/export), trade system used (General vs Special trade), import/export valuation method (CIF vs FOB), partner country attribution rules, and publication notes. Essential for understanding how to interpret the trade values in comtrade.trade_data results. Each country reports using its own methodology and currency — this endpoint reveals those details. Source: UN Comtrade public preview API, no auth. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
comtrade.trade.metadata accepts 6 parameters: period, freq_code, type_code, show_history, reporter_code, classification. Required: period, reporter_code. 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 comtrade.trade.metadata: 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.
comtrade.trade.metadata 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 comtrade.trade.metadata 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 comtrade.trade.metadata. 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.
comtrade.trade.metadata 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