crm_dismiss_merge_proposal
Mark a pending merge proposal as dismissed (the operator decided these are not the same person). The next CRM hygiene curator pass queries dismissed proposals and skips refiling the same pair. Optional
This record as markdown: /tools/com-getmunin-munin/crm-dismiss-merge-proposal.md
What crm_dismiss_merge_proposal does on Munin
AI agents use crm_dismiss_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_dismiss_merge_proposal is rated Medium
The tool creates or modifies data in a reversible manner: it updates the status of a merge proposal from pending to dismissed, allowing future hygiene processes to skip that pair. This is not destructive (the proposal record remains and could theoretically be reconsidered) and not a read operation since it has a side effect.
From the tool's definition Tool name contains 'dismiss' (a state change), and description explicitly states 'Mark a pending merge proposal as dismissed', indicating the tool modifies stored state—specifically flagging a merge proposal record with dismissed status.
Attacks that exploit this kind of access
The rule that runs crm_dismiss_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_dismiss_merge_proposal, this is the rule to start with:
crm_dismiss_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_dismiss_merge_proposal call is checked against it from then on.
Questions about crm_dismiss_merge_proposal
Mark a pending merge proposal as dismissed (the operator decided these are not the same person). The next CRM hygiene curator pass queries dismissed proposals and skips refiling the same pair. Optional. 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_dismiss_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_dismiss_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_dismiss_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_dismiss_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_dismiss_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