crm_search_contacts

Search contacts with contact-specific filters

SERVERHubSpot MCP SOURCEblacksand-software/hubspot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/blacksand-software-hubspot-mcp/crm-search-contacts.md

WHAT IT DOES

What crm_search_contacts does on HubSpot MCP

AI agents call crm_search_contacts to retrieve information from HubSpot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why crm_search_contacts is rated Low

This tool retrieves contact data based on search criteria. Searching is a read-only operation that queries existing data without side effects. While the HubSpot server includes destructive and write operations (batch_create, batch_update, batch_archive), this specific tool is narrowly scoped to search/query, placing it squarely in the Read category with low severity due to its non-destructive nature.

From the tool's definition Tool name 'crm_search_contacts' and description 'Search contacts with contact-specific filters' indicate querying/searching functionality with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crm_search_contacts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and HubSpot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_search_contacts, this is the rule to start with:

crm_search_contacts Allowed

crm_search_contacts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crm_search_contacts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect HubSpot MCP, apply this rule, and every crm_search_contacts call is checked against it from then on.

FAQ

Questions about crm_search_contacts

What does the crm_search_contacts tool do? +

Search contacts with contact-specific filters. It is categorised as a Read tool in the HubSpot MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crm_search_contacts? +

Register the HubSpot MCP server in PolicyLayer and add a rule for crm_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 HubSpot MCP. Nothing to install.

What risk level is crm_search_contacts? +

crm_search_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crm_search_contacts? +

Yes. Add a rate_limit block to the crm_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.

How do I block crm_search_contacts completely? +

Set action: deny in the PolicyLayer policy for crm_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.

What MCP server provides crm_search_contacts? +

crm_search_contacts is provided by the HubSpot MCP server (blacksand-software/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on HubSpot, and thousands of servers like it.

This server

All 111 HubSpot tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →