outreach_update_campaign
Patch fields on a campaign — rename, swap segment, adjust cadence, toggle enabled, toggle the automation flags
This record as markdown: /tools/com-getmunin-munin/outreach-update-campaign.md
What outreach_update_campaign does on Munin
AI agents use outreach_update_campaign 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_update_campaign is rated Medium
Modifies campaign configuration settings reversibly; changes can be undone or re-adjusted without permanent data loss.
From the tool's definition Patch fields on a campaign — rename, swap segment, adjust cadence, toggle enabled
Attacks that exploit this kind of access
The rule that runs outreach_update_campaign 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_update_campaign, this is the rule to start with:
outreach_update_campaign 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_update_campaign call is checked against it from then on.
Questions about outreach_update_campaign
Patch fields on a campaign — rename, swap segment, adjust cadence, toggle enabled, toggle the automation flags. 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_update_campaign: 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_update_campaign 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_update_campaign 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_update_campaign. 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_update_campaign 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