Low Risk

ic_list_companies

List companies with pagination. Returns company ID, name, website, employee count, and custom attributes.

Part of the Intercom server.

ic_list_companies is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE INTERCOM →

Free to start. No card required.

AI agents call ic_list_companies to retrieve information from Intercom without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though ic_list_companies only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ic_list_companies": {}
  }
}

See the full Intercom policy for all 25 tools.

Get this rule live on your own Intercom server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY INTERCOM →

View all 25 tools →

These attack patterns abuse exactly the kind of access ic_list_companies gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ic_list_companies only ever does what you allow.

SECURE INTERCOM →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the ic_list_companies tool do? +

List companies with pagination. Returns company ID, name, website, employee count, and custom attributes.. It is categorised as a Read tool in the Intercom MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ic_list_companies? +

Register the Intercom MCP server in PolicyLayer and add a rule for ic_list_companies: 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 Intercom. Nothing to install.

What risk level is ic_list_companies? +

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

Can I rate-limit ic_list_companies? +

Yes. Add a rate_limit block to the ic_list_companies 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 ic_list_companies completely? +

Set action: deny in the PolicyLayer policy for ic_list_companies. 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 ic_list_companies? +

ic_list_companies is provided by the Intercom MCP server (https://gateway.pipeworx.io/intercom/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Intercom tool call.

Deterministic rules across all 25 Intercom tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.