Search leads with lead-specific filters
AI agents call crm_search_leads to retrieve information from HubSpot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves lead records based on filters but does not create, modify, delete, or execute any operations. It has no side effects on data state. While HubSpot CRM can contain sensitive contact information, the read-only nature and typical query scope limit the blast radius to information disclosure rather than system compromise or data destruction.
From the tool's definition Tool name 'crm_search_leads' combined with description 'Search leads with lead-specific filters' indicates a query operation that retrieves lead data without modification. The verb 'search' is explicitly a read operation.
Attacks that exploit this kind of access
Search leads with lead-specific filters. It is categorised as a Read tool in the HubSpot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HubSpot MCP Server MCP server in PolicyLayer and add a rule for crm_search_leads: 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 HubSpot MCP Server. Nothing to install.
crm_search_leads 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 crm_search_leads 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 crm_search_leads. 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.
crm_search_leads is provided by the HubSpot MCP Server MCP server (kozo93/hubspot-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 →