Low Risk

consultar_diarios_municipais

Busca publicações em diários oficiais municipais via Querido Diário (OK.org.br).

Risk signalsAccepts freeform code/query input (query)

Part of the DataBR server.

consultar_diarios_municipais 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 DATABR →

Free to start. No card required.

AI agents call consultar_diarios_municipais 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_diarios_municipais 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": {
    "consultar_diarios_municipais": {}
  }
}

See the full DataBR policy for all 82 tools.

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

ENFORCE ON MY DATABR →

View all 82 tools →

These attack patterns abuse exactly the kind of access consultar_diarios_municipais 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 consultar_diarios_municipais only ever does what you allow.

SECURE DATABR →

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

What does the consultar_diarios_municipais tool do? +

Busca publicações em diários oficiais municipais via Querido Diário (OK.org.br).. 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_diarios_municipais? +

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

What risk level is consultar_diarios_municipais? +

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

Can I rate-limit consultar_diarios_municipais? +

Yes. Add a rate_limit block to the consultar_diarios_municipais 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 consultar_diarios_municipais completely? +

Set action: deny in the PolicyLayer policy for consultar_diarios_municipais. 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_diarios_municipais? +

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

Enforce policy on every DataBR tool call.

Deterministic rules across all 82 DataBR 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.