Get a delivery for an organization webhook
AI agents call get_organization_webhook_delivery to retrieve information from Mcp Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical webhook delivery information for auditing or debugging purposes. It is a read-only operation with no side effects—it does not create, modify, delete, or execute operations. The blast radius if misused is minimal: an attacker could enumerate webhook deliveries to understand webhook activity, but cannot alter infrastructure or trigger actions.
From the tool's definition Tool name 'get_organization_webhook_delivery' and description 'Get a delivery for an organization webhook' indicate a retrieval operation that queries webhook delivery data without modification.
Attacks that exploit this kind of access
Get a delivery for an organization webhook. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.
Register the Mcp Github MCP server in PolicyLayer and add a rule for get_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.
get_organization_webhook_delivery is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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 →