simulate_new_email
Fire a Unipile mail_received webhook. Use to test inbound email handling — reply detection, chat thread creation, and campaign execution advancement.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/simulate-new-email.md
What simulate_new_email does on Max MCP Server
AI agents invoke simulate_new_email to trigger actions in Max MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why simulate_new_email is rated High
This tool executes a simulated email event that triggers downstream processing logic (reply detection, thread creation, campaign state changes). While framed as a testing utility, it performs Execute-category actions: firing webhooks and advancing campaign state. It's not purely Read (no side effects) nor Write (not just creating/modifying data reversibly—it actively triggers automation).
From the tool's definition Tool description states it 'Fire[s] a Unipile mail_received webhook' and is used to 'test inbound email handling — reply detection, chat thread creation, and campaign execution advancement.' This triggers external operations (webhook firing, email simulation,…
Attacks that exploit this kind of access
The rule that runs simulate_new_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For simulate_new_email, this is the rule to start with:
simulate_new_email stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every simulate_new_email call is checked against it from then on.
Questions about simulate_new_email
Fire a Unipile mail_received webhook. Use to test inbound email handling — reply detection, chat thread creation, and campaign execution advancement. It is categorised as a Execute tool in the Max MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for simulate_new_email: 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 Max MCP Server. Nothing to install.
simulate_new_email is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the simulate_new_email 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 simulate_new_email. 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.
simulate_new_email is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
Across the catalogue