Use this tool to find conversations in Intercom based on filters such as status, contact ID, or assigned admin. Call it when you need to see all open tickets for a specific customer, find unassigned conversations, or retrieve a list of conversations matching any combination of criteria before rep...
AI agents call search_conversations to retrieve information from Intercom MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_conversations retrieves and queries conversation data based on filters without creating, modifying, or deleting any data. It is a pure read operation used to gather information before other actions (replying, assigning, closing) are taken. The blast radius if misused is minimal—an agent could retrieve conversations it shouldn't access, but cannot alter system state or cause irreversible harm.
From the tool's definition Tool description explicitly states "find conversations", "retrieve a list of conversations" with filtering by status, contact ID, or assigned admin. No modification, deletion, or execution of external operations is performed.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Use this tool to find conversations in Intercom based on filters such as status, contact ID, or assigned admin. Call it when you need to see all open tickets for a specific customer, find unassigned conversations, or retrieve a list of conversations matching any combination of criteria before replying, assigning, or closing them. It is categorised as a Read tool in the Intercom MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Intercom MCP Server MCP server in PolicyLayer and add a rule for search_conversations: 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.
search_conversations 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 search_conversations 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 search_conversations. 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.
search_conversations 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 →