redeliver_repository_webhook_delivery

WHAT IT DOES

What redeliver_repository_webhook_delivery does on Mcp Github

AI agents invoke redeliver_repository_webhook_delivery to trigger actions in Mcp Github. 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 redeliver_repository_webhook_delivery needs a policy

Redelivering a webhook retriggers an outbound HTTP call to an external endpoint, causing side effects that depend on what the receiving system does. This is an external operation execution rather than a simple read or write, and could cause repeated processing, duplicate events, or unintended downstream actions.

From the tool's definition "Redeliver a repository webhook delivery" — triggers re-execution of an external webhook HTTP request

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

redeliver_repository_webhook_delivery Rate-limited

redeliver_repository_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": {
    "redeliver_repository_webhook_delivery": {
      "limits": [
        {
          "counter": "redeliver_repository_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 Mcp Github, so you can run agents against it safely.

FAQ

Questions about redeliver_repository_webhook_delivery

What does the redeliver_repository_webhook_delivery tool do? +

Redeliver a repository webhook delivery. It is categorised as a Execute tool in the Mcp Github MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on redeliver_repository_webhook_delivery? +

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

What risk level is redeliver_repository_webhook_delivery? +

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

Can I rate-limit redeliver_repository_webhook_delivery? +

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

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

redeliver_repository_webhook_delivery is provided by the Mcp Github MCP server (@missionsquad/mcp-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.