Use this tool to send a reply to an existing Intercom conversation. Call it when you need to respond to a customer message on behalf of an admin, or when you need to add an internal note that is only visible to your team (not the customer). You must provide the conversation ID and the admin ID se...
AI agents use reply_to_conversation to create or update resources in Intercom MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intercom MCP Server environment.
This tool creates new data (conversation replies or internal notes) that are added to Intercom conversations. It is reversible (replies can typically be deleted or edited in most support systems) and does not execute arbitrary code, delete data, or involve financial transactions.
From the tool's definition Tool description states "send a reply to an existing Intercom conversation" and "respond to a customer message on behalf of an admin" or "add an internal note".
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Use this tool to send a reply to an existing Intercom conversation. Call it when you need to respond to a customer message on behalf of an admin, or when you need to add an internal note that is only visible to your team (not the customer). You must provide the conversation ID and the admin ID sending the reply. It is categorised as a Write tool in the Intercom MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intercom MCP Server MCP server in PolicyLayer and add a rule for reply_to_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 Intercom MCP Server. Nothing to install.
reply_to_conversation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reply_to_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 reply_to_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.
reply_to_conversation is provided by the Intercom MCP Server MCP server (shackletonanalytics/intercom-mcp-server). 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 →