redrive_mailbox_webhook_delivery · Run402 MCP: Risk & Policy

WHAT IT DOES

What redrive_mailbox_webhook_delivery does on Run402

AI agents invoke redrive_mailbox_webhook_delivery to trigger actions in Run402. 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 IT NEEDS A POLICY

Why redrive_mailbox_webhook_delivery needs a policy

This tool triggers an external operation — re-attempting a webhook delivery to a consumer endpoint. It causes the system to re-execute an outbound HTTP request, which is an execution of an external action. It does not merely read data, nor does it permanently delete anything, nor does it involve finances.

From the tool's definition Re-queue a dead-lettered (failed_permanent) webhook delivery so the worker attempts delivery again

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

redrive_mailbox_webhook_delivery Rate-limited

redrive_mailbox_webhook_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": {
    "redrive_mailbox_webhook_delivery": {
      "limits": [
        {
          "counter": "redrive_mailbox_webhook_delivery_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Run402, so you can run agents against it safely.

FAQ

Questions about redrive_mailbox_webhook_delivery

What does the redrive_mailbox_webhook_delivery tool do? +

Re-queue a dead-lettered (failed_permanent) webhook delivery so the worker attempts delivery again. Use after fixing the consumer endpoint. It is categorised as a Execute tool in the Run402 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on redrive_mailbox_webhook_delivery? +

Register the Run402 MCP server in PolicyLayer and add a rule for redrive_mailbox_webhook_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 Run402. Nothing to install.

What risk level is redrive_mailbox_webhook_delivery? +

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

Can I rate-limit redrive_mailbox_webhook_delivery? +

Yes. Add a rate_limit block to the redrive_mailbox_webhook_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 redrive_mailbox_webhook_delivery completely? +

Set action: deny in the PolicyLayer policy for redrive_mailbox_webhook_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 redrive_mailbox_webhook_delivery? +

redrive_mailbox_webhook_delivery is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

redrive_mailbox_webhook_delivery is one line of Run402's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →