List deliveries for a repository webhook
AI agents call list_repository_webhook_deliveries 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 and displays webhook delivery history/metadata without modifying, deleting, or executing any operations. It is purely informational, making it a Read category risk with low severity. The blast radius of misuse is minimal—an actor could view webhook delivery details but cannot alter or act upon them.
From the tool's definition 'List deliveries for a repository webhook' is a query operation that retrieves historical webhook delivery records. The verb 'list' and the action of viewing webhook deliveries indicates data retrieval with no side effects.
Attacks that exploit this kind of access
List deliveries 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 list_repository_webhook_deliveries: 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.
list_repository_webhook_deliveries 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 list_repository_webhook_deliveries 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 list_repository_webhook_deliveries. 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.
list_repository_webhook_deliveries 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 →