Send an email message to a lead.
AI agents use sendEmail to create or update resources in Lofty MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lofty MCP Server environment.
Sending email is a reversible write operation that creates or appends data to a lead's communication log. It is not destructive (email can be recalled or marked as spam), not financial (no money movement), and not execute-class (no arbitrary code/shell operations).
From the tool's definition Tool description states 'Send an email message to a lead' — this creates a new email communication artifact that modifies the lead's interaction history and outbound messaging record.
Attacks that exploit this kind of access
Send an email message to a lead. It is categorised as a Write tool in the Lofty MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for sendEmail: 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 Lofty MCP Server. Nothing to install.
sendEmail 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 sendEmail 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 sendEmail. 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.
sendEmail is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-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 →