Search HubSpot deals using query string
AI agents call search_deals 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 performs a read-only search operation on deal data in HubSpot CRM. It retrieves and queries information with no side effects—no data is created, modified, deleted, or executed. The risk is low because even if an AI agent searches for deals with arbitrary or malicious query strings, the worst outcome is information disclosure of deals the authenticated user already has access to.
From the tool's definition Tool name 'search_deals' and description 'Search HubSpot deals using query string' indicate a query/search operation that retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
Search HubSpot deals using query string. 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 search_deals: 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.
search_deals 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 search_deals 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 search_deals. 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.
search_deals is provided by the HubSpot MCP Server MCP server (sanketskasar/hubspot-mcp-server). 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 →