AI agents use sendEvent 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 and transmits custom event records associated with email accounts. While it modifies data (events are written to a system), it does not permanently delete data (not Destructive), move money (not Financial), or execute arbitrary code (not Execute).
From the tool's definition Tool name 'sendEvent' and description 'Send custom events with email, event name and event properties' indicates creation/writing of event data. The term 'Send' combined with custom event creation confirms data modification.
Attacks that exploit this kind of access
Send custom events with email, event name and event properties. 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 sendEvent: 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.
sendEvent 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 sendEvent 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 sendEvent. 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.
sendEvent 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 →