get_email_message
Get detailed email message information by email message ID
This record as markdown: /tools/ghl/get-email-message.md
What get_email_message does on Ghl
AI agents call get_email_message 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 |
|---|---|---|---|
emailMessageId | string | Yes | The unique ID of the email message to retrieve |
Parameters from the server's own tool schema.
Why get_email_message is rated Low
This tool retrieves and queries existing email message data without modifying, deleting, or executing any operations. It is a straightforward read operation that fetches information based on an identifier. The blast radius of misuse is low—an AI agent could retrieve unintended email details, but cannot modify, delete, or execute actions with this tool alone.
From the tool's definition Tool name 'get_email_message' and description 'Get detailed email message information by email message ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_email_message 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_email_message, this is the rule to start with:
get_email_message 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_email_message call is checked against it from then on.
Questions about get_email_message
Get detailed email message information by email message ID. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_email_message accepts 1 parameter: emailMessageId. Required: emailMessageId. 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_email_message: 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_email_message 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_email_message 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_email_message. 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_email_message 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