Low Risk

contaazul_list_accounts

Lista as empresas Conta Azul vinculadas a este install (company_id, label).

Part of the Conta Azul MCP server.

contaazul_list_accounts 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 CONTA AZUL MCP →

Free to start. No card required.

AI agents call contaazul_list_accounts to retrieve information from Conta Azul MCP 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 contaazul_list_accounts 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": {
    "contaazul_list_accounts": {}
  }
}

See the full Conta Azul MCP policy for all 37 tools.

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

ENFORCE ON MY CONTA AZUL MCP →

View all 37 tools →

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

SECURE CONTA AZUL MCP →

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

What does the contaazul_list_accounts tool do? +

Lista as empresas Conta Azul vinculadas a este install (company_id, label).. It is categorised as a Read tool in the Conta Azul MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on contaazul_list_accounts? +

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

What risk level is contaazul_list_accounts? +

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

Can I rate-limit contaazul_list_accounts? +

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

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

contaazul_list_accounts is provided by the Conta Azul MCP server (https://api.mcp.ai/contaazul). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Conta Azul MCP tool call.

Deterministic rules across all 37 Conta Azul MCP 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.