get_all_objects
Get all objects (custom and standard) for a location including contact, opportunity, business, and custom objects
This record as markdown: /tools/ghl/get-all-objects.md
What get_all_objects does on Ghl
AI agents call get_all_objects 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 |
|---|---|---|---|
locationId | string | — | Location ID (uses default if not provided) |
Parameters from the server's own tool schema.
Why get_all_objects is rated Low
This tool retrieves/queries data (contacts, opportunities, businesses, custom objects) for a location without side effects. No creation, modification, deletion, or execution occurs. Severity is medium because the retrieved data likely contains sensitive business and customer information that could be exposed if an agent misuses this tool to aggregate and exfiltrate data.
From the tool's definition Tool name 'get_all_objects' and description 'Get all objects...including contact, opportunity, business, and custom objects' indicates data retrieval with no modification or deletion. The verb 'Get' is a classic read operation.
Attacks that exploit this kind of access
The rule that runs get_all_objects 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 get_all_objects, this is the rule to start with:
get_all_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 Ghl, apply this rule, and every get_all_objects call is checked against it from then on.
Questions about get_all_objects
Get all objects (custom and standard) for a location including contact, opportunity, business, and custom objects. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_all_objects accepts 1 parameter: locationId. 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 get_all_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 Ghl. Nothing to install.
get_all_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 get_all_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 get_all_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.
get_all_objects 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