AI agents call hs_contact_by_email to retrieve information from Hubspot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact data based on an email address search parameter. It is a non-destructive read operation that queries existing CRM data without creating, modifying, deleting, or executing any external actions. The return of 'up to 5 matches' confirms it is a search/retrieval function.
From the tool's definition Tool name 'hs_contact_by_email' and description 'Look up contacts by exact email address. Returns up to 5 matches' indicate a query/lookup operation with no side effects.
Attacks that exploit this kind of access
Look up contacts by exact email address. Returns up to 5 matches. It is categorised as a Read tool in the Hubspot MCP Server, which means it retrieves data without modifying state.
Register the Hubspot MCP server in PolicyLayer and add a rule for hs_contact_by_email: 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. Nothing to install.
hs_contact_by_email 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 hs_contact_by_email 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 hs_contact_by_email. 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.
hs_contact_by_email is provided by the Hubspot MCP server (zleventer/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 →