Reply to a specific message. Sends your response to the original sender and removes the original from your inbox. Always reply to messages that ask you a question or request information.
AI agents use reply to create or update resources in Claude Intercom — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Intercom environment.
The tool sends a message (creates new outbound data) and removes the original from the inbox. The removal aspect could be considered mildly destructive, but since it's an inbox management side-effect of a reply action (similar to 'mark as read/archive'), the dominant action is creating/sending a reply message — a Write operation.
From the tool's definition Reply to a specific message. Sends your response to the original sender and removes the original from your inbox.
Attacks that exploit this kind of access
Reply to a specific message. Sends your response to the original sender and removes the original from your inbox. Always reply to messages that ask you a question or request information. It is categorised as a Write tool in the Claude Intercom MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Intercom MCP server in PolicyLayer and add a rule for reply: 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 Claude Intercom. Nothing to install.
reply 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 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. 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 is provided by the Claude Intercom MCP server (sanztheo/claude-intercom). 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 →