intercom_search_contacts

Search Intercom contacts by email or name.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/intercom-search-contacts.md

WHAT IT DOES

What intercom_search_contacts does on Integrations MCP

AI agents call intercom_search_contacts to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why intercom_search_contacts is rated Low

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

RECOMMENDED RULE

The rule that runs intercom_search_contacts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For intercom_search_contacts, this is the rule to start with:

intercom_search_contacts Allowed

intercom_search_contacts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "intercom_search_contacts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every intercom_search_contacts call is checked against it from then on.

FAQ

Questions about intercom_search_contacts

What does the intercom_search_contacts tool do? +

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.

How do I enforce a policy on intercom_search_contacts? +

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.

What risk level is intercom_search_contacts? +

intercom_search_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit intercom_search_contacts? +

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.

How do I block intercom_search_contacts completely? +

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.

What MCP server provides intercom_search_contacts? +

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.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →