Comexstat Data Server (Brazilian foreign trade statistics)

20 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
20 read-only
20 tools total
Read (20) Write / Execute (0) Destructive / Financial (0)

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

Cap read operations
getAuxiliaryTable:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Is the Comexstat Data Server (Brazilian foreign trade statistics) MCP server safe to use without restrictions? +

The Comexstat Data Server (Brazilian foreign trade statistics) server is primarily read-only with 20 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Comexstat Data Server (Brazilian foreign trade statistics) MCP server expose? +

20 tools across 1 categories: Read. 20 are read-only. 0 can modify, create, or delete data.

How do I add Intercept to my Comexstat Data Server (Brazilian foreign trade statistics) setup? +

One line change. Instead of running the Comexstat Data Server (Brazilian foreign trade statistics) server directly, prefix it with Intercept: intercept -c luizzzvictor-mcp-comexstat.yaml -- npx -y @luizzzvictor/mcp-comexstat. Download a pre-built policy from policylayer.com/policies/luizzzvictor-mcp-comexstat and adjust the limits to match your use case.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.