This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/intercom-list-contacts.md
What intercom_list_contacts does on UnClick
AI agents call intercom_list_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 |
|---|---|---|---|
limit | number | — | Contacts to return (max 150, default 25) |
access_token | string | Yes | Intercom access token |
starting_after | string | — | Pagination cursor from a previous response |
Parameters from the server's own tool schema.
Why intercom_list_contacts is rated Low
The verb 'list' is a classic Read operation—it retrieves and displays contact information from Intercom without side effects. No creation, modification, deletion, or execution of external operations occurs.
From the tool's definition Tool name 'intercom_list_contacts' with description 'List Intercom contacts' indicates a retrieval operation that queries existing contact data without modification.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs intercom_list_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_list_contacts, this is the rule to start with:
intercom_list_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_list_contacts call is checked against it from then on.
Questions about intercom_list_contacts
List Intercom contacts. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
intercom_list_contacts accepts 3 parameters: limit, access_token, starting_after. Required: 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_list_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_list_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_list_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_list_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_list_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