crm_change_deal_stage
Move a deal to a new stage. If the destination stage is a won/lost terminal,
This record as markdown: /tools/com-getmunin-munin/crm-change-deal-stage.md
What crm_change_deal_stage does on Munin
AI agents use crm_change_deal_stage 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.
Why crm_change_deal_stage is rated Medium
Modifies CRM deal stage; potentially irreversible if moved to terminal won/lost state.
From the tool's definition Move a deal to a new stage, won/lost terminal
Attacks that exploit this kind of access
The rule that runs crm_change_deal_stage 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_change_deal_stage, this is the rule to start with:
crm_change_deal_stage 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every crm_change_deal_stage call is checked against it from then on.
Questions about crm_change_deal_stage
Move a deal to a new stage. If the destination stage is a won/lost terminal,. 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.
Register the Munin MCP server in PolicyLayer and add a rule for crm_change_deal_stage: 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_change_deal_stage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crm_change_deal_stage 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_change_deal_stage. 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_change_deal_stage 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