Get the activity history for a lead (stage changes, updates).
AI agents call get_lead_history to retrieve information from Outlet das Cores CRM without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries past activity records for a lead (stage changes and updates). It is a read-only operation that returns data without creating, modifying, deleting, or executing external actions. The blast radius of misuse is minimal—an agent could only access historical information about a lead, which does not affect system state or cause harm beyond potential information disclosure.
From the tool's definition Tool name 'get_lead_history' and description 'Get the activity history for a lead (stage changes, updates)' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
Get the activity history for a lead (stage changes, updates). It is categorised as a Read tool in the Outlet das Cores CRM MCP Server, which means it retrieves data without modifying state.
Register the Outlet das Cores CRM MCP server in PolicyLayer and add a rule for get_lead_history: 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 Outlet das Cores CRM. Nothing to install.
get_lead_history 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 get_lead_history 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 get_lead_history. 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.
get_lead_history is provided by the Outlet das Cores CRM MCP server (oeduardomanoel/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 →