outreach_propose_reply
File a drafted reply to an inbound message on an outreach-originated conversation, for human approval. The conversation must have an
This record as markdown: /tools/com-getmunin-munin/outreach-propose-reply.md
What outreach_propose_reply does on Munin
AI agents use outreach_propose_reply 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 outreach_propose_reply is rated Medium
This tool creates new draft message content in a conversation context. While it modifies the conversation state by adding a draft reply, the explicit requirement for 'human approval' before execution means the actual message send is gated and reversible. This qualifies as Write rather than Execute, as the tool itself does not autonomously send messages—it only drafts them.
From the tool's definition Tool name contains 'propose_reply' and description states 'File a drafted reply to an inbound message', indicating creation of new message content. Description emphasizes 'for human approval', indicating the action is reversible and not executed autonomously.
Attacks that exploit this kind of access
The rule that runs outreach_propose_reply 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_propose_reply, this is the rule to start with:
outreach_propose_reply 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 outreach_propose_reply call is checked against it from then on.
Questions about outreach_propose_reply
File a drafted reply to an inbound message on an outreach-originated conversation, for human approval. The conversation must have an. 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 outreach_propose_reply: 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_propose_reply 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 outreach_propose_reply 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_propose_reply. 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_propose_reply 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