Create an email campaign that can be sent to a contact list.
AI agents use create_campaign to create or update resources in XEM Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your XEM Email MCP Server environment.
Creating a campaign is a Write operation—it generates new data (campaign configuration) without irreversibly deleting anything or executing external code directly. However, severity is elevated to 'medium' rather than 'low' because campaigns can be leveraged to send bulk communications (phishing, spam) if an AI agent misuses this tool with malicious intent, especially when combined with sibling tools like…
From the tool's definition Tool 'create_campaign' is described as creating an email campaign, which is a reversible data creation operation.
Attacks that exploit this kind of access
Create an email campaign that can be sent to a contact list. It is categorised as a Write tool in the XEM Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the XEM Email MCP Server MCP server in PolicyLayer and add a rule for create_campaign: 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 XEM Email MCP Server. Nothing to install.
create_campaign 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_campaign 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_campaign. 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_campaign is provided by the XEM Email MCP Server MCP server (mailxem/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 →