get_object_record
Get a specific record by ID from a custom or standard object
This record as markdown: /tools/ghl/get-object-record.md
What get_object_record does on Ghl
AI agents call get_object_record 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 |
|---|---|---|---|
recordId | string | Yes | ID of the record to retrieve |
schemaKey | string | Yes | Schema key of the object |
Parameters from the server's own tool schema.
Why get_object_record is rated Low
This tool retrieves data by ID without modifying, deleting, or executing operations. It performs a simple lookup/query operation typical of read-only database access. The low severity reflects that retrieval of existing data has minimal blast radius compared to write, execute, or destructive operations.
From the tool's definition Tool description states 'Get a specific record by ID from a custom or standard object' - the verb 'Get' and the retrieval-only nature indicate this is a read operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_object_record 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_object_record, this is the rule to start with:
get_object_record 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_object_record call is checked against it from then on.
Questions about get_object_record
Get a specific record by ID from a custom or standard object. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_object_record accepts 2 parameters: recordId, schemaKey. Required: recordId, 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 get_object_record: 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_object_record 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_object_record 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_object_record. 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_object_record 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