get_conversation_messages
Get messages from a specific conversation thread. Shows the chat history between the merchant and a contact.
This record as markdown: /tools/io-favcrm-favcrm/get-conversation-messages.md
What get_conversation_messages does on FavCRM
AI agents call get_conversation_messages to retrieve information from FavCRM 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 | — | Max results (default 20) |
search | string | — | Search within messages |
conversationId | string | Yes | The conversation ID |
Parameters from the server's own tool schema.
Why get_conversation_messages is rated Low
This tool retrieves historical conversation data without creating, modifying, deleting, or executing any operations. It is a straightforward query operation that poses minimal risk if called by an AI agent, as it only exposes existing message data accessible to the authenticated user.
From the tool's definition Tool description states 'Get messages from a specific conversation thread' and 'Shows the chat history' — both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_conversation_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_conversation_messages, this is the rule to start with:
get_conversation_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 FavCRM, apply this rule, and every get_conversation_messages call is checked against it from then on.
Questions about get_conversation_messages
Get messages from a specific conversation thread. Shows the chat history between the merchant and a contact. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_conversation_messages accepts 3 parameters: limit, search, conversationId. Required: conversationId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for get_conversation_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 FavCRM. Nothing to install.
get_conversation_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_conversation_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_conversation_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_conversation_messages is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue