crm_list_contacts_in_segment
Resolve a segment to its current contacts. ALWAYS excludes suppressed contacts (do_not_contact OR unsubscribed) AND contacts without a recorded lawful basis (consent_lawful_basis IS NULL). Use this — not crm_list_contacts — to materialize an outreach audience: the suppression and consent floors a...
This record as markdown: /tools/com-getmunin-munin/crm-list-contacts-in-segment.md
What crm_list_contacts_in_segment does on Munin
AI agents call crm_list_contacts_in_segment 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.
Why crm_list_contacts_in_segment is rated Low
This tool retrieves/queries contact data from a CRM segment. The built-in enforcement of suppression and consent filters ("non-overridable") makes this a safe, read-only query operation. No data is created, modified, deleted, or written. No external actions are triggered.
From the tool's definition Tool name uses 'list' verb and description states it 'Resolve[s] a segment to its current contacts' — a retrieval operation with no modifications.
Attacks that exploit this kind of access
The rule that runs crm_list_contacts_in_segment 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_contacts_in_segment, this is the rule to start with:
crm_list_contacts_in_segment 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 Munin, apply this rule, and every crm_list_contacts_in_segment call is checked against it from then on.
Questions about crm_list_contacts_in_segment
Resolve a segment to its current contacts. ALWAYS excludes suppressed contacts (do_not_contact OR unsubscribed) AND contacts without a recorded lawful basis (consent_lawful_basis IS NULL). Use this — not crm_list_contacts — to materialize an outreach audience: the suppression and consent floors are non-overridable here. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for crm_list_contacts_in_segment: 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.
crm_list_contacts_in_segment 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 crm_list_contacts_in_segment 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 crm_list_contacts_in_segment. 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.
crm_list_contacts_in_segment 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.
More on Munin, and thousands of servers like it.
This server
Across the catalogue