AI agents use addBulkContactToList to create or update resources in Mailmodo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailmodo environment.
This tool creates or modifies data (adds contacts to a mailing list) in a reversible manner. It does not delete data, execute arbitrary code, or move money, making it a Write operation. The severity is medium because bulk operations on contact lists could enable spam, unauthorized marketing, or data pollution, but the impact is limited to list membership changes without permanent destruction.
From the tool's definition Tool name 'addBulkContactToList' and description 'Add Many Contact to a list in single API' indicate creation/addition of multiple contacts to an existing list.
Attacks that exploit this kind of access
Add Many Contact to a list in single API. It is categorised as a Write tool in the Mailmodo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mailmodo MCP server in PolicyLayer and add a rule for addBulkContactToList: 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 Mailmodo. Nothing to install.
addBulkContactToList 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 addBulkContactToList 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 addBulkContactToList. 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.
addBulkContactToList is provided by the Mailmodo MCP server (mailmodo/mailmodo-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 →