Reply to an Intercom conversation as an admin. Use this to send a message visible to the customer.
AI agents use reply_conversation to create or update resources in Intercom Articles MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intercom Articles MCP Server environment.
The tool creates new message content in conversations, modifying the conversation state by adding admin replies. This is a Write operation (creates/modifies data reversibly) rather than Read (no new data created), Execute (doesn't run code or trigger external logic based on dynamic arguments), or Destructive (messages can be deleted or edited, making it reversible).
From the tool's definition Tool description states: 'Reply to an Intercom conversation as an admin. Use this to send a message visible to the customer.' This creates and adds new communication content (a reply message) to an existing conversation, which is a reversible write operation.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access reply_conversation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intercom Articles MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reply_conversation:
{
"version": "1",
"default": "deny",
"tools": {
"reply_conversation": {
"limits": [
{
"counter": "reply_conversation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reply_conversation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reply to an Intercom conversation as an admin. Use this to send a message visible to the customer. It is categorised as a Write tool in the Intercom Articles MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intercom Articles MCP Server MCP server in PolicyLayer and add a rule for reply_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 Articles MCP Server. Nothing to install.
reply_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_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_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_conversation is provided by the Intercom Articles MCP Server MCP server (kaosensei/intercom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intercom Articles MCP Server, 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.
16 Intercom Articles MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.