Low Risk

consultar_ipea

Consulta séries temporais do IPEA por código, busca por nome, ou lista temas.

Part of the DataBR MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

databr/api Read

AI agents call consultar_ipea to retrieve information from DataBR 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 consultar_ipea 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.

databr-api.yaml
tools:
  consultar_ipea:
    rules:
      - action: allow

See the full DataBR policy for all 82 tools.

Tool Name consultar_ipea
Category Read
MCP Server DataBR MCP Server
Risk Level Low

View all 82 tools →

Agents calling read-class tools like consultar_ipea have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the consultar_ipea tool do? +

Consulta séries temporais do IPEA por código, busca por nome, ou lista temas.. It is categorised as a Read tool in the DataBR MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on consultar_ipea? +

Add a rule in your Intercept YAML policy under the tools section for consultar_ipea. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the DataBR MCP server.

What risk level is consultar_ipea? +

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

Can I rate-limit consultar_ipea? +

Yes. Add a rate_limit block to the consultar_ipea rule in your Intercept 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 consultar_ipea completely? +

Set action: deny in the Intercept policy for consultar_ipea. 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 consultar_ipea? +

consultar_ipea is provided by the DataBR MCP server (databr/api). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on DataBR

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.