intercom_get_conversation
Get a single Intercom conversation by id.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/intercom-get-conversation.md
What intercom_get_conversation does on UnClick
AI agents call intercom_get_conversation 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 |
|---|---|---|---|
access_token | string | Yes | Intercom access token |
conversation_id | string | Yes | Conversation id |
Parameters from the server's own tool schema.
Why intercom_get_conversation is rated Low
This tool queries and retrieves an existing conversation record from Intercom. It performs a read-only operation with no data modification, deletion, code execution, or financial impact. The low severity reflects minimal blast radius if misused — an agent could retrieve conversation data it shouldn't access, but cannot modify or delete messages, trigger actions, or cause irreversible harm.
From the tool's definition Tool name contains 'get' and description states 'Get a single Intercom conversation by id' — retrieves data with no modifications or side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs intercom_get_conversation 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_get_conversation, this is the rule to start with:
intercom_get_conversation 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_get_conversation call is checked against it from then on.
Questions about intercom_get_conversation
Get a single Intercom conversation by id. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
intercom_get_conversation accepts 2 parameters: access_token, conversation_id. Required: access_token, conversation_id. 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_get_conversation: 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_get_conversation 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_get_conversation 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_get_conversation. 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_get_conversation 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