Get activity history for a lead (v2, cursor/offset-based with timezone support).
AI agents call getLeadActivitiesV2 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 retrieves historical activity data associated with a lead in the CRM system. The operation is a query that returns information without modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could retrieve excessive data or access activity history it shouldn't, but no data would be altered or deleted.
From the tool's definition Tool name 'getLeadActivities' and description 'Get activity history for a lead' clearly indicates a retrieval operation with no side effects. The mention of 'cursor/offset-based' pagination and 'timezone support' are read-only parameters for data retrieval.
Attacks that exploit this kind of access
Get activity history for a lead (v2, cursor/offset-based with timezone support). 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 getLeadActivitiesV2: 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.
getLeadActivitiesV2 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 getLeadActivitiesV2 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 getLeadActivitiesV2. 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.
getLeadActivitiesV2 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 →