outreach_withdraw_proposal
Retract one pending outreach proposal that should no longer be reviewed — a duplicate draft, a prospect who turned out not to qualify, a bounced address. Nothing is sent. This is a neutral retraction, not a rejection: it does not suppress the contact, does not change their consent, and does not s...
This record as markdown: /tools/com-getmunin-munin/outreach-withdraw-proposal.md
What outreach_withdraw_proposal does on Munin
AI agents use outreach_withdraw_proposal to commit financial operations through Munin, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why outreach_withdraw_proposal is rated Critical
outreach_withdraw_proposal moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs outreach_withdraw_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 outreach_withdraw_proposal, this is the rule to start with:
Any call to outreach_withdraw_proposal is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every outreach_withdraw_proposal call is checked against it from then on.
Questions about outreach_withdraw_proposal
Retract one pending outreach proposal that should no longer be reviewed — a duplicate draft, a prospect who turned out not to qualify, a bounced address. Nothing is sent. This is a neutral retraction, not a rejection: it does not suppress the contact, does not change their consent, and does not stop a campaign sequence (a withdrawn follow-up leaves later steps eligible, unlike a dismissed one). A required. It is categorised as a Financial tool in the Munin MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Munin MCP server in PolicyLayer and add a rule for outreach_withdraw_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.
outreach_withdraw_proposal is a Financial 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 outreach_withdraw_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 outreach_withdraw_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.
outreach_withdraw_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.
Across the catalogue