// MCP TOOL REFERENCE

GITHUB WEBHOOK TOOLS

5 tools from the Github Webhook MCP Server, categorised by risk level.

READ TOOLS

get_event Get the full payload for a single webhook event by ID. get_pending_status Get a lightweight snapshot of pending GitHub webhook events. Use this for periodic polling before requesting details. get_webhook_events Get pending (unprocessed) GitHub webhook events with full payloads. Prefer get_pending_status or list_pending_events for polling. list_pending_events List lightweight summaries for pending GitHub webhook events. Returns metadata only, without full payloads.

WRITE TOOLS

mark_processed Mark a webhook event as processed so it won't appear again. 2/5

// FAQ

How many tools does the Github Webhook MCP server have? +

The Github Webhook MCP server exposes 5 tools across 2 categories: Read, Write.

How do I enforce policies on Github Webhook tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Github Webhook server.

What risk categories do Github Webhook tools fall into? +

Github Webhook tools are categorised as Read (4), Write (1). Each category has a recommended default policy.

Enforce policies on Github Webhook

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →