Get activity history for a lead (v1, page-based).
AI agents call getLeadActivitiesV1 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 for a lead in a CRM system. It performs a search/fetch operation with no side effects, reversible changes, or external operations. The page-based pagination mechanism further confirms this is a simple data retrieval endpoint. No financial, destructive, or code execution capabilities are present.
From the tool's definition Tool name 'getLeadActivitiesV1' and description 'Get activity history for a lead' indicate a retrieval operation with no modification capability. The verb 'Get' and context of retrieving 'activity history' clearly denote a read-only data query.
Attacks that exploit this kind of access
Get activity history for a lead (v1, page-based). 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 getLeadActivitiesV1: 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.
getLeadActivitiesV1 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 getLeadActivitiesV1 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 getLeadActivitiesV1. 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.
getLeadActivitiesV1 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 →