crm_apply_merge_proposal
Atomically apply a pending merge proposal: copies
This record as markdown: /tools/com-getmunin-munin/crm-apply-merge-proposal.md
What crm_apply_merge_proposal does on Munin
AI agents use crm_apply_merge_proposal 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_apply_merge_proposal is rated Medium
The tool creates or modifies CRM data by applying a merge proposal, which consolidates records. While the description is truncated ('copies' is incomplete), the intent is clearly to perform a data modification operation. This is Write rather than Destructive because merges are typically reversible (the original records may be recoverable) and the operation is conditional on an existing proposal.
From the tool's definition Tool name is 'crm_apply_merge_proposal' and description states it 'Atomically apply a pending merge proposal: copies' — this modifies customer/contact records by merging data, a reversible write operation.
Attacks that exploit this kind of access
The rule that runs crm_apply_merge_proposal 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_apply_merge_proposal, this is the rule to start with:
crm_apply_merge_proposal 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_apply_merge_proposal call is checked against it from then on.
Questions about crm_apply_merge_proposal
Atomically apply a pending merge proposal: copies. 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_apply_merge_proposal: 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_apply_merge_proposal 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_apply_merge_proposal 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_apply_merge_proposal. 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_apply_merge_proposal 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