crm_update_segment

Patch a segment: rename, edit description, or replace the filter.

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

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/crm-update-segment.md

WHAT IT DOES

What crm_update_segment does on Munin

AI agents use crm_update_segment to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.

RISK

Why crm_update_segment is rated Medium

This tool creates or modifies segment configuration data (name, description, filter criteria) in a reversible manner. Users can undo these changes by editing the segment again. It does not delete data (Destructive), execute arbitrary operations (Execute), retrieve data without side effects (Read), or involve financial transactions (Financial).

From the tool's definition Tool name 'crm_update_segment' and description 'Patch a segment: rename, edit description, or replace the filter' indicate modification of existing segment data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

crm_update_segment Rate-limited

crm_update_segment stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crm_update_segment": {
      "limits": [
        {
          "counter": "crm_update_segment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about crm_update_segment

What does the crm_update_segment tool do? +

Patch a segment: rename, edit description, or replace the filter. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crm_update_segment? +

Register the Munin MCP server in PolicyLayer and add a rule for crm_update_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.

What risk level is crm_update_segment? +

crm_update_segment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit crm_update_segment? +

Yes. Add a rate_limit block to the crm_update_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.

How do I block crm_update_segment completely? +

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

What MCP server provides crm_update_segment? +

crm_update_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.

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →