This record as markdown: /tools/com-getmunin-munin/conv-test-email-channel.md
What conv_test_email_channel does on Munin
AI agents invoke conv_test_email_channel to trigger actions in Munin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why conv_test_email_channel is rated High
Testing an email channel involves executing an external operation that sends a real or simulated email through the configured channel. This is not a pure read (it has side effects) nor a write (it doesn't persist data changes), but rather triggers an external communication action. Misuse could result in unwanted emails being sent to real addresses.
From the tool's definition 'Test an email channel' — triggers an external operation (sending a test email) to verify channel configuration
Attacks that exploit this kind of access
The rule that runs conv_test_email_channel 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_test_email_channel, this is the rule to start with:
conv_test_email_channel stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_test_email_channel call is checked against it from then on.
Questions about conv_test_email_channel
Test an email channel\. It is categorised as a Execute tool in the Munin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Munin MCP server in PolicyLayer and add a rule for conv_test_email_channel: 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_test_email_channel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the conv_test_email_channel 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_test_email_channel. 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_test_email_channel 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