Redeliver an organization webhook delivery
AI agents invoke redeliver_organization_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.
Redelivering a webhook triggers an external HTTP request to the webhook endpoint, re-executing the delivery of a previously sent payload. This is an external operation with side effects (re-triggering downstream systems), placing it in the Execute category. It doesn't create or modify data directly, nor is it destructive or financial.
From the tool's definition Redeliver an organization webhook delivery
Attacks that exploit this kind of access
Redeliver an organization 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.
Register the Mcp Github MCP server in PolicyLayer and add a rule for redeliver_organization_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.
redeliver_organization_webhook_delivery 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 redeliver_organization_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.
Set action: deny in the PolicyLayer policy for redeliver_organization_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.
redeliver_organization_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →