search_object_records
Search records within a custom or standard object using searchable properties
This record as markdown: /tools/ghl/search-object-records.md
What search_object_records does on Ghl
AI agents call search_object_records to retrieve information from Ghl 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 |
|---|---|---|---|
page | number | — | Page number for pagination |
query | string | Yes | Search query using searchable properties (e.g., "name:Buddy" to search for records with name Buddy) |
pageLimit | number | — | Number of records per page |
schemaKey | string | Yes | Schema key of the object to search in |
locationId | string | — | Location ID (uses default if not provided) |
searchAfter | array | — | Cursor for pagination (returned from previous search) |
Parameters from the server's own tool schema.
Why search_object_records is rated Low
This tool retrieves or queries data without creating, modifying, deleting, or executing actions. It is a standard Read operation typical of database or CRM query functionality. The low severity reflects that searching records alone poses minimal risk unless the search scope exposes highly sensitive data, but the operation itself is non-destructive and reversible.
From the tool's definition Tool name contains 'search' and description explicitly states 'Search records within a custom or standard object using searchable properties' — a query operation with no side effects.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs search_object_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_object_records, this is the rule to start with:
search_object_records 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 Ghl, apply this rule, and every search_object_records call is checked against it from then on.
Questions about search_object_records
Search records within a custom or standard object using searchable properties. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
search_object_records accepts 6 parameters: page, query, pageLimit, schemaKey, locationId, searchAfter. Required: query, schemaKey. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for search_object_records: 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 Ghl. Nothing to install.
search_object_records 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_object_records 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_object_records. 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_object_records is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue