This record as markdown: /tools/com-getmunin-munin/outreach-import.md
What outreach_import does on Munin
AI agents use outreach_import 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_import is rated Medium
This tool imports outreach data, which creates or adds new records to the outreach module of the customer platform. This is a Write operation as it modifies the system state by introducing new data. Severity is medium because bulk imports could affect customer relationship data, but the operation is reversible (records can be deleted).
From the tool's definition Tool name 'outreach_import' and description 'Import outreach' indicate data ingestion/creation. The 'import' verb typically creates or adds records to a system.
Attacks that exploit this kind of access
The rule that runs outreach_import 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_import, this is the rule to start with:
outreach_import 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_import call is checked against it from then on.
Questions about outreach_import
Import outreach. 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_import: 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_import 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_import 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_import. 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_import 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