List all transactions for a lead.
AI agents call listLeadTransactions 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 tool queries and retrieves transaction data associated with a lead without modifying, deleting, or executing any external operations. It is a straightforward read operation typical of CRM data retrieval endpoints. The low severity reflects minimal risk if misused by an AI agent, as viewing transaction history poses no direct harm to data integrity or business operations.
From the tool's definition Tool name 'listLeadTransactions' and description 'List all transactions for a lead' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all transactions 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 listLeadTransactions: 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.
listLeadTransactions 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 listLeadTransactions 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 listLeadTransactions. 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.
listLeadTransactions 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 →