intercom_list_conversations
List recent Intercom conversations.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/intercom-list-conversations.md
What intercom_list_conversations does on UnClick
AI agents call intercom_list_conversations to retrieve information from UnClick 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 | — | Conversations to return (max 150, default 20) |
access_token | string | Yes | Intercom access token |
starting_after | string | — | Pagination cursor from a previous response |
Parameters from the server's own tool schema.
Why intercom_list_conversations is rated Low
This tool retrieves conversation metadata from Intercom without creating, modifying, deleting, or executing anything. It is a straightforward read operation. Severity is low because listing conversations exposes potentially sensitive messaging data, but the blast radius is limited to information disclosure rather than data loss or unauthorized actions.
From the tool's definition Tool name contains 'list' and description explicitly states 'List recent Intercom conversations' — a query operation that retrieves data with no modification or side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs intercom_list_conversations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For intercom_list_conversations, this is the rule to start with:
intercom_list_conversations 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 UnClick, apply this rule, and every intercom_list_conversations call is checked against it from then on.
Questions about intercom_list_conversations
List recent Intercom conversations. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
intercom_list_conversations accepts 3 parameters: limit, access_token, starting_after. Required: access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for intercom_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 UnClick. Nothing to install.
intercom_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 intercom_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 intercom_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.
intercom_list_conversations is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue