Get a delivery for a repository webhook
AI agents call get_repository_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 webhook delivery information from GitHub without creating, modifying, deleting, or executing any code. It is a read-only query operation that has no side effects on the repository or its data. The low severity reflects minimal risk even if accessed inappropriately, as it only exposes webhook delivery metadata/logs.
From the tool's definition Tool name 'get_repository_webhook_delivery' and description 'Get a delivery for a repository webhook' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Get a delivery for a repository 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_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.
get_repository_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_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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 →