Search Intercom contacts by email or name.
AI agents call intercom_search_contacts 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 or queries contact information from Intercom—a typical Read operation. The search parameters (email, name) are safe filters for data retrieval. The blast radius of misuse is minimal: exposure of contact information is the primary risk, which is lower severity than Write, Execute, Destructive, or Financial categories.
From the tool's definition The tool 'intercom_search_contacts' performs a search operation by email or name, which is a query function that retrieves contact data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Search Intercom contacts by email or name. 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_search_contacts: 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_search_contacts 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_search_contacts 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_search_contacts. 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_search_contacts 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 →