get_recent_messages
Get recent messages across all conversations for monitoring
This record as markdown: /tools/ghl/get-recent-messages.md
What get_recent_messages does on Ghl
AI agents call get_recent_messages 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 |
|---|---|---|---|
limit | number | — | Maximum number of conversations to check (default: 10) |
status | string | — | Filter by conversation status |
Parameters from the server's own tool schema.
Why get_recent_messages is rated Low
This tool retrieves existing message data without creating, modifying, deleting, or executing any operations. It is a read-only monitoring function that queries message history across conversations, which is the canonical use case for the Read category.
From the tool's definition Tool name 'get_recent_messages' and description 'Get recent messages across all conversations for monitoring' indicate data retrieval only. The verb 'Get' and the purpose 'for monitoring' confirm this is a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_recent_messages 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_recent_messages, this is the rule to start with:
get_recent_messages 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_recent_messages call is checked against it from then on.
Questions about get_recent_messages
Get recent messages across all conversations for monitoring. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_recent_messages accepts 2 parameters: limit, status. 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_recent_messages: 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_recent_messages 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_recent_messages 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_recent_messages. 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_recent_messages 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