Low Risk

ibge_malhas

Gets geographic meshes (maps) from IBGE in GeoJSON, TopoJSON, or SVG format. Features: - Meshes for Brazil, regions, states, municipalities - Different resolution levels (internal divisions) - Different quality levels - Formats: GeoJSON (data), TopoJSON (compact), SVG (image) Locality types: - "B...

Risk signalsBulk/mass operation — affects multiple targets

Part of the Ibge Br server.

ibge_malhas is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE IBGE BR →

Free to start. No card required.

AI agents call ibge_malhas to retrieve information from Ibge Br without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though ibge_malhas only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ibge_malhas": {}
  }
}

See the full Ibge Br policy for all 23 tools.

Get this rule live on your own Ibge Br server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY IBGE BR →

View all 23 tools →

These attack patterns abuse exactly the kind of access ibge_malhas gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ibge_malhas only ever does what you allow.

SECURE IBGE BR →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the ibge_malhas tool do? +

Gets geographic meshes (maps) from IBGE in GeoJSON, TopoJSON, or SVG format. Features: - Meshes for Brazil, regions, states, municipalities - Different resolution levels (internal divisions) - Different quality levels - Formats: GeoJSON (data), TopoJSON (compact), SVG (image) Locality types: - "BR" or "1" = Entire Brazil - State abbreviation (e.g., "SP", "RJ") - State code (e.g., "35" for SP) - Municipality code (7 digits) Resolution (internal divisions): - 0 = Outline only - 2 = States - 5 = Municipalities Examples: - Brazil with states: localidade="BR", resolucao="2" - São Paulo with municipalities: localidade="SP", resolucao="5" - SVG format: localidade="BR", formato="svg". It is categorised as a Read tool in the Ibge Br MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ibge_malhas? +

Register the Ibge Br MCP server in PolicyLayer and add a rule for ibge_malhas: 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 Ibge Br. Nothing to install.

What risk level is ibge_malhas? +

ibge_malhas is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ibge_malhas? +

Yes. Add a rate_limit block to the ibge_malhas 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.

How do I block ibge_malhas completely? +

Set action: deny in the PolicyLayer policy for ibge_malhas. 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.

What MCP server provides ibge_malhas? +

ibge_malhas is provided by the Ibge Br MCP server (ibge-br-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ibge Br tool call.

Deterministic rules across all 23 Ibge Br tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.