This record as markdown: /tools/aiwerk-mcp-server-ghl/objects-search-object-records.md
What objects_search_object_records does on Ghl
AI agents call objects_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 | Yes | Page |
query | string | Yes | Pass this query parameter to search using your searchable properties. For example, if you have a custom object called “Pets” and have configured “name” as a sea |
pageLimit | number | Yes | Page Limit |
schemaKey | string | Yes | custom object key |
locationId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
searchAfter | array | Yes |
Parameters from the server's own tool schema.
Why objects_search_object_records is rated Low
Even though objects_search_object_records only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs objects_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 objects_search_object_records, this is the rule to start with:
objects_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 objects_search_object_records call is checked against it from then on.
Questions about objects_search_object_records
Search Object Records. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
objects_search_object_records accepts 6 parameters: page, query, pageLimit, schemaKey, locationId, searchAfter. Required: page, query, pageLimit, schemaKey, searchAfter. 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 objects_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.
objects_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 objects_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 objects_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.
objects_search_object_records is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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