Create a new contact list.
AI agents use create-contact-list to create or update resources in Mcp Mailtrap — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mailtrap environment.
This tool creates/adds data without permanently deleting or overwriting existing data, and does not execute arbitrary code or move money. It fits the Write category. Severity is medium because misuse could lead to unauthorized creation of contact lists affecting email campaign organization, but the impact is reversible and localized to data structures rather than bulk financial or destructive operations.
From the tool's definition create-contact-list is described as creating a new contact list. The verb 'create' indicates the tool adds new data (a contact list) to the Mailtrap system in a reversible manner.
Attacks that exploit this kind of access
Create a new contact list. It is categorised as a Write tool in the Mcp Mailtrap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for create-contact-list: 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 Mcp Mailtrap. Nothing to install.
create-contact-list 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 create-contact-list 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 create-contact-list. 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.
create-contact-list is provided by the Mcp Mailtrap MCP server (mcp-mailtrap). 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 →