wto.trade.reporters
List all 288 reporting economies (countries and economic groups) recognized by the WTO time-series database, with their 3-digit numeric codes, ISO 3-letter country codes, and display names. Use these codes in wto.trade.data reporter_codes and partner_codes parameters. Includes individual WTO memb...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wto.trade.reporters.md
What wto.trade.reporters does on Apibase
AI agents call wto.trade.reporters 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 |
|---|---|---|---|
filter | string | — | Optional case-insensitive substring to filter reporters by name (e.g. "European", "Africa", "United"). Applied client-side — returns full list if omitted (288 e |
Parameters from the server's own tool schema.
Why wto.trade.reporters is rated Low
Tool retrieves reference data about WTO reporting entities without side effects or data modification.
From the tool's definition List all 288 reporting economies with codes and names, filter client-side
Attacks that exploit this kind of access
The rule that runs wto.trade.reporters 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.reporters, this is the rule to start with:
wto.trade.reporters 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.reporters call is checked against it from then on.
Questions about wto.trade.reporters
List all 288 reporting economies (countries and economic groups) recognized by the WTO time-series database, with their 3-digit numeric codes, ISO 3-letter country codes, and display names. Use these codes in wto.trade.data reporter_codes and partner_codes parameters. Includes individual WTO members (e.g. 840=USA, 156=China, 276=Germany, 392=Japan, 356=India, 036=Australia), geographic aggregates (e.g. 097=European Union, 413=LDC group), and the world total (000=World). Filter results client-side by name substring (e.g. "Africa", "European", "United") to find the relevant codes for your query. Data sourced from the WTO Statistics Division; economy composition reflects WTO membership. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wto.trade.reporters accepts 1 parameter: filter. 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.reporters: 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.reporters 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.reporters 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.reporters. 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.reporters 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