register_mailbox_webhook · Run402 MCP: Risk & Policy

WHAT IT DOES

What register_mailbox_webhook does on Run402

AI agents use register_mailbox_webhook to create or update resources in Run402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Run402 environment.

WHY IT NEEDS A POLICY

Why register_mailbox_webhook needs a policy

Registering a webhook creates a new persistent binding that modifies project configuration. This is a Write operation (reversible configuration change) rather than Execute because the tool itself does not trigger actions—it sets up infrastructure for future event notifications.

From the tool's definition Tool name 'register_mailbox_webhook' and description 'Register a webhook on the project' indicate the creation/registration of a new webhook, which is a persistent configuration modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_mailbox_webhook Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "register_mailbox_webhook": {
      "limits": [
        {
          "counter": "register_mailbox_webhook_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 register_mailbox_webhook

What does the register_mailbox_webhook tool do? +

Register a webhook on the project. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on register_mailbox_webhook? +

Register the Run402 MCP server in PolicyLayer and add a rule for register_mailbox_webhook: 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 register_mailbox_webhook? +

register_mailbox_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit register_mailbox_webhook? +

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

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

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