hubspot_search_contacts
Search HubSpot contacts by name, email, or company.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/hubspot-search-contacts.md
What hubspot_search_contacts does on UnClick
AI agents call hubspot_search_contacts to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Results to return (max 100, default 25) |
query | string | Yes | Search term (name, email, or company) |
properties | string | — | Comma-separated properties to return |
access_token | string | Yes | HubSpot Private App access token |
Parameters from the server's own tool schema.
Why hubspot_search_contacts is rated Low
This tool retrieves contact information from HubSpot based on search criteria. It performs a read-only query with no side effects on data. While contact data may be sensitive, the tool itself only searches/retrieves existing information without modifying, deleting, or executing operations. The blast radius is limited to information disclosure.
From the tool's definition Tool name contains 'search' and description states 'Search HubSpot contacts by name, email, or company' - a pure query operation with no modification, deletion, or execution of commands.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs hubspot_search_contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hubspot_search_contacts, this is the rule to start with:
hubspot_search_contacts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every hubspot_search_contacts call is checked against it from then on.
Questions about hubspot_search_contacts
Search HubSpot contacts by name, email, or company. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hubspot_search_contacts accepts 4 parameters: limit, query, properties, access_token. Required: query, access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for hubspot_search_contacts: 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 UnClick. Nothing to install.
hubspot_search_contacts 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 hubspot_search_contacts 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 hubspot_search_contacts. 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.
hubspot_search_contacts is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue