crm_list_segments

List saved contact segments. A segment is a named CRM filter — used as the audience for outreach campaigns and other targeting workflows. Returns each segment with its filter definition.

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/crm-list-segments.md

WHAT IT DOES

What crm_list_segments does on Munin

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

RISK

Why crm_list_segments is rated Low

This tool retrieves segment definitions and metadata from the CRM system for viewing/querying purposes. It has no side effects: it does not create, modify, delete, or execute actions. The blast radius is minimal—an AI agent misuse would at worst expose segment definitions that the user already has access to. No data is modified, destroyed, or financial obligations incurred.

From the tool's definition Tool name includes 'list' and description states 'List saved contact segments' with 'Returns each segment' — classic read/query pattern with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crm_list_segments safely

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

crm_list_segments Allowed

crm_list_segments 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": {
    "crm_list_segments": {}
  }
}

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

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

FAQ

Questions about crm_list_segments

What does the crm_list_segments tool do? +

List saved contact segments. A segment is a named CRM filter — used as the audience for outreach campaigns and other targeting workflows. Returns each segment with its filter definition. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crm_list_segments? +

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

What risk level is crm_list_segments? +

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

Can I rate-limit crm_list_segments? +

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

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

crm_list_segments is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_get_rfm_segments on AIVA MCP Server → The MCP Attack Database →

Guides

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