This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/brevo-list-contacts.md
What brevo_list_contacts does on UnClick
AI agents call brevo_list_contacts to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Contacts to return (max 1000, default 50) |
offset | number | — | Pagination offset |
api_key | string | Yes | Brevo API key |
Parameters from the server's own tool schema.
Why brevo_list_contacts is rated Low
The tool performs a read operation by listing/retrieving contacts from Brevo (an email marketing platform). There is no indication of data modification, deletion, execution of commands, or financial transactions. The blast radius of misuse is low—an attacker gains visibility into contact lists but cannot alter, delete, or exfiltrate at scale without additional tools.
From the tool's definition Tool name 'brevo_list_contacts' and description 'List Brevo contacts' indicate a retrieval operation that queries contact data without modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs brevo_list_contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brevo_list_contacts, this is the rule to start with:
brevo_list_contacts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every brevo_list_contacts call is checked against it from then on.
Questions about brevo_list_contacts
List Brevo contacts. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
brevo_list_contacts accepts 3 parameters: limit, offset, api_key. Required: api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for brevo_list_contacts: 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 UnClick. Nothing to install.
brevo_list_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the brevo_list_contacts 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.
Set action: deny in the PolicyLayer policy for brevo_list_contacts. 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.
brevo_list_contacts is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue