intercom_list_contacts

List contacts in Intercom with pagination.

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-list-contacts.md

WHAT IT DOES

What intercom_list_contacts does on Integrations MCP

AI agents call intercom_list_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_list_contacts is rated Low

This tool queries and retrieves contact data from Intercom with pagination support. It performs a read-only operation that has no side effects on data—it neither creates, modifies, deletes, nor executes actions. The blast radius is minimal as it only returns existing contact information accessible through normal API permissions. Classified as Read with low severity.

From the tool's definition Tool name 'intercom_list_contacts' and description 'List contacts in Intercom with pagination' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs intercom_list_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_list_contacts, this is the rule to start with:

intercom_list_contacts Allowed

intercom_list_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_list_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_list_contacts call is checked against it from then on.

FAQ

Questions about intercom_list_contacts

What does the intercom_list_contacts tool do? +

List contacts in Intercom with pagination. 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_list_contacts? +

Register the Integrations 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 Integrations MCP. Nothing to install.

What risk level is intercom_list_contacts? +

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

Can I rate-limit intercom_list_contacts? +

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.

How do I block intercom_list_contacts completely? +

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.

What MCP server provides intercom_list_contacts? +

intercom_list_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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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