crm_search_objects
Search CRM objects using filters
This record as markdown: /tools/blacksand-software-hubspot-mcp/crm-search-objects.md
What crm_search_objects does on HubSpot MCP
AI agents call crm_search_objects 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.
Why crm_search_objects is rated Low
This tool retrieves or queries CRM data without side effects. Search operations are classified as Read category. Severity is low because unauthorized search access, while concerning for privacy, does not directly compromise data integrity or enable destructive actions. The HubSpot CRM context suggests access to business contact and deal data, but search alone cannot modify or delete records.
From the tool's definition Tool name 'crm_search_objects' with description 'Search CRM objects using filters' indicates a query/search operation. The sibling tools show a pattern of read (list, get, search), write (create, update), and batch operations.
Attacks that exploit this kind of access
The rule that runs crm_search_objects 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_objects, this is the rule to start with:
crm_search_objects 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 HubSpot MCP, apply this rule, and every crm_search_objects call is checked against it from then on.
Questions about crm_search_objects
Search CRM objects using filters. It is categorised as a Read tool in the HubSpot MCP MCP Server, which means it retrieves data without modifying state.
Register the HubSpot MCP server in PolicyLayer and add a rule for crm_search_objects: 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.
crm_search_objects 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_objects 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_objects. 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_objects 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.
More on HubSpot, and thousands of servers like it.
This server
Across the catalogue