This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/intercom-search-contacts.md
What intercom_search_contacts does on UnClick
AI agents call intercom_search_contacts to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Email (or partial email) to match |
access_token | string | Yes | Intercom access token |
Parameters from the server's own tool schema.
Why intercom_search_contacts is rated Low
This is a read-only operation that searches and retrieves existing contact data from Intercom. It has no side effects, does not modify data, and does not trigger external operations. The blast radius is limited to potential information disclosure of contact details, which is a low-severity risk if misused by an AI agent.
From the tool's definition The tool 'intercom_search_contacts' with description 'Search Intercom contacts by email' performs a query operation that retrieves contact information without modifying, deleting, or executing external actions.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs intercom_search_contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every intercom_search_contacts call is checked against it from then on.
Questions about intercom_search_contacts
Search Intercom contacts by email. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
intercom_search_contacts accepts 2 parameters: query, access_token. Required: query, access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue