Process inbound emails and attachments
AI agents use inbound to create or update resources in Brevo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brevo MCP Server environment.
The tool processes inbound emails and attachments, which involves ingesting external data into the system. While it reads incoming emails, the primary action is to process and store them, creating or modifying records within Brevo's system. This constitutes a Write operation rather than pure Read.
From the tool's definition Tool name 'inbound' with description 'Process inbound emails and attachments' indicates receiving and handling email data.
Attacks that exploit this kind of access
Process inbound emails and attachments. It is categorised as a Write tool in the Brevo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for inbound: 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 Brevo MCP Server. Nothing to install.
inbound is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the inbound 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 inbound. 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.
inbound is provided by the Brevo MCP Server MCP server (samihalawa/brevo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →