search-object-records

Supported Objects are custom objects and standard objects like

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-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/drausal-gohighlevel-mcp/search-object-records.md

WHAT IT DOES

What search-object-records does on GoHighLevel MCP Server

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

RISK

Why search-object-records is rated Low

This is a search/query tool that retrieves records from a database without creating, modifying, deleting, or executing side effects. It falls clearly into the Read category with low severity since search operations have no destructive blast radius.

From the tool's definition Tool name 'search-object-records' combined with server description stating it 'interact[s] with GoHighLevel's complete API' for querying contacts, opportunities, calendars, and other business data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search-object-records safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, 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 Allowed

search-object-records 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": {
    "search-object-records": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every search-object-records call is checked against it from then on.

FAQ

Questions about search-object-records

What does the search-object-records tool do? +

Supported Objects are custom objects and standard objects like. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search-object-records? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is search-object-records? +

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

Can I rate-limit search-object-records? +

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.

How do I block search-object-records completely? +

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.

What MCP server provides search-object-records? +

search-object-records is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 406 GoHighLevel MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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