Retrieves Intercom conversations within a specific date range. Required: startDate, endDate (DD/MM/YYYY format, max 7-day range) Optional: keyword, exclude (for content filtering) Always ask for specific dates when user makes vague time references.
AI agents call list_conversations to retrieve information from MCP Server for Intercom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval of existing conversation data from Intercom. It queries conversations by date range and optional filters but does not create, modify, delete, or execute operations. The 7-day range restriction and read-only nature further indicate low risk. No side effects or irreversible actions are possible.
From the tool's definition Tool name is 'list_conversations' and description states it 'Retrieves Intercom conversations within a specific date range'.
Documented attack patterns abuse exactly the kind of access list_conversations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Intercom, and nothing reaches the server without passing your rules. This is the rule we recommend for list_conversations:
{
"version": "1",
"default": "deny",
"tools": {
"list_conversations": {}
}
}list_conversations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves Intercom conversations within a specific date range. Required: startDate, endDate (DD/MM/YYYY format, max 7-day range) Optional: keyword, exclude (for content filtering) Always ask for specific dates when user makes vague time references. It is categorised as a Read tool in the MCP Server for Intercom MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Intercom MCP server in PolicyLayer and add a rule for list_conversations: 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 MCP Server for Intercom. Nothing to install.
list_conversations 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 list_conversations 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 list_conversations. 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.
list_conversations is provided by the MCP Server for Intercom MCP server (raoulbia-ai/mcp-server-for-intercom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Intercom, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 MCP Server for Intercom tools catalogued and risk-classified — across an index of 43,000+ MCP servers.