Get full details of an Intercom conversation including messages.
AI agents call intercom_get_conversation to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves conversation data from Intercom without modifying, deleting, or executing any operations. It is a straightforward read operation. While conversations may contain sensitive customer communication, the blast radius of accidental misuse is limited to information disclosure rather than data loss, system compromise, or financial impact.
From the tool's definition Tool name contains 'get' and description states 'Get full details of an Intercom conversation including messages' — a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get full details of an Intercom conversation including messages. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations 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 Integrations MCP. 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 Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →