List email communication history for a lead.
AI agents call listEmailHistory to retrieve information from Lofty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves existing data (email history) for a lead. It has no side effects, does not create, modify, or delete data, and does not trigger external operations or financial transactions. The blast radius of misuse is minimal—an agent could access communication history it shouldn't see, but cannot alter or act upon it destructively.
From the tool's definition The tool name 'listEmailHistory' and description 'List email communication history for a lead' indicate a query operation that retrieves historical email data without modifying, deleting, or executing actions.
Attacks that exploit this kind of access
List email communication history for a lead. It is categorised as a Read tool in the Lofty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for listEmailHistory: 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.
listEmailHistory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listEmailHistory 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 listEmailHistory. 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.
listEmailHistory 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 →