conv_retry_delivery

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/conv-retry-delivery.md

WHAT IT DOES

What conv_retry_delivery does on Munin

AI agents invoke conv_retry_delivery 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.

RISK

Why conv_retry_delivery is rated High

Triggers an external delivery operation by re-queuing a failed message send.

From the tool's definition Re-queue the outbound delivery of an outgoing message that permanently failed

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs conv_retry_delivery 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_retry_delivery, this is the rule to start with:

conv_retry_delivery Rate-limited

conv_retry_delivery 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "conv_retry_delivery": {
      "limits": [
        {
          "counter": "conv_retry_delivery_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every conv_retry_delivery call is checked against it from then on.

FAQ

Questions about conv_retry_delivery

What does the conv_retry_delivery tool do? +

Re-queue the outbound delivery of an outgoing message that permanently failed to send. Outbound email and SMS are delivered by a background worker that retries five times with exponential backoff; after the last attempt the delivery is marked. 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.

How do I enforce a policy on conv_retry_delivery? +

Register the Munin MCP server in PolicyLayer and add a rule for conv_retry_delivery: 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.

What risk level is conv_retry_delivery? +

conv_retry_delivery is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit conv_retry_delivery? +

Yes. Add a rate_limit block to the conv_retry_delivery 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.

How do I block conv_retry_delivery completely? +

Set action: deny in the PolicyLayer policy for conv_retry_delivery. 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.

What MCP server provides conv_retry_delivery? +

conv_retry_delivery 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.

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →