This record as markdown: /tools/ghl/get-message-recording.md
What get_message_recording does on Ghl
AI agents call get_message_recording 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 |
|---|---|---|---|
messageId | string | Yes | The unique ID of the call message to get recording for |
Parameters from the server's own tool schema.
Why get_message_recording is rated Low
This tool retrieves pre-existing call recording audio data. While the classification is straightforward as a Read operation (fetching/retrieving data), the severity is elevated to medium rather than low because call recordings are sensitive personal data containing private conversations, voice identification information, and potentially confidential business discussions.
From the tool's definition Tool description states it 'Get call recording audio for a message' - a retrieval operation with no side effects that queries/fetches existing data.
Attacks that exploit this kind of access
The rule that runs get_message_recording 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_message_recording, this is the rule to start with:
get_message_recording 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_message_recording call is checked against it from then on.
Questions about get_message_recording
Get call recording audio for a message. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_message_recording accepts 1 parameter: messageId. Required: messageId. 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_message_recording: 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_message_recording 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_message_recording 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_message_recording. 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_message_recording 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