This record as markdown: /tools/com-getmunin-munin/conv-import.md
What conv_import does on Munin
AI agents use conv_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 conv_import is rated Medium
Import operations create or populate data structures (conversations) from external sources, which is a Write operation. Severity is medium because bulk imports could overwrite or duplicate existing data, but the impact is reversible. Confidence is 0.85 rather than higher because the description lacks detail about whether this overwrites existing data, affects only new records, or has side effects on linked entities.
From the tool's definition Tool name 'conv_import' and description 'Import conversation' indicate creation or ingestion of conversation data, which modifies the system state by adding new records.
Attacks that exploit this kind of access
The rule that runs conv_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 conv_import, this is the rule to start with:
conv_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 conv_import call is checked against it from then on.
Questions about conv_import
Import conversation. 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 conv_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.
conv_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 conv_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 conv_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.
conv_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