crm_delete_segment
Delete a segment. Outreach campaigns referencing it will fail until reassigned.
This record as markdown: /tools/com-getmunin-munin/crm-delete-segment.md
What crm_delete_segment does on Munin
AI agents call crm_delete_segment to permanently remove resources in Munin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crm_delete_segment is rated Critical
This tool permanently removes a segment from the CRM system, which is a Destructive action (irreversible data deletion). The high severity reflects that deletion breaks dependent outreach campaigns, creating cascading effects that require manual intervention to repair. The confidence is high because the name 'delete' and description unambiguously indicate permanent removal.
From the tool's definition 'Delete a segment' indicates irreversible deletion; the description explicitly states 'Outreach campaigns referencing it will fail until reassigned,' showing destructive side effects that cannot be automatically undone.
Attacks that exploit this kind of access
The rule that runs crm_delete_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_delete_segment, this is the rule to start with:
crm_delete_segment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every crm_delete_segment call is checked against it from then on.
Questions about crm_delete_segment
Delete a segment. Outreach campaigns referencing it will fail until reassigned. It is categorised as a Destructive tool in the Munin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Munin MCP server in PolicyLayer and add a rule for crm_delete_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_delete_segment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the crm_delete_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_delete_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_delete_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.
Across the catalogue