Repository navigation
Conversation
Add pages for Connector Gateway and AI Gateway policy webhooks, and link them from the sidebar and related pages. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
🟡 Changes recommended
The documentation overstates ToolHive receiver compatibility and needs to distinguish shared request/response formats from gateway-specific restrictions, particularly the rejection of tool-name patches.
1 open issue
What changed in this PR
Adds policy webhook guides for the Connector Gateway and AI Gateway, helping operators connect their own policy services to gateway request processing.
Changes:
- Documents webhook configuration, execution order, receiver contracts, and failure handling.
- Covers authentication, network access, monitoring, and troubleshooting.
- Adds sidebar entries and links from the existing access-policy guides.
| File | Description |
|---|---|
sidebars.ts |
Adds navigation entries for both webhook guides. |
docs/connector-gateway/policy-webhooks.mdx |
Explains tool-call validation, mutation, and receiver setup. |
docs/connector-gateway/connector-policies.mdx |
Links connector access policies to the webhook guide. |
docs/ai-gateway/policy-webhooks.mdx |
Explains request and completion hooks, enforcement, and receiver setup. |
docs/ai-gateway/control-model-access.mdx |
Links model access controls to the webhook guide. |
Review effort: Balanced
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
amirejaz
left a comment
There was a problem hiding this comment.
Thanks for writing this up. I checked the AI Gateway page against the gateway and chart code on main. Most of it is accurate: the field table and its limits, the phase and enforcement rules, the call order after the built-in checks, the WebhookReview field names, the deny-message format, the retry triggers, the completion timeout rules, and the render-time and startup checks all match.
The inline comments cover the places where a customer would be misled or caught out. The ones that matter most are:
- What a
requiredresponse.completedwebhook does to traffic without usage. - The CA-rotation restart.
networkPolicy.enableddefaulting tofalse.- Malformed
2xxanswers blocking the response.
I haven't reviewed the Connector Gateway page here.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Visual regression failedThe visual job failed, but CI could not produce a compact screenshot summary. Details were unavailable because the Playwright artifact is unavailable. Open the failed visual job · Download the full Playwright report If the change is intentional, a repository collaborator can comment |
amirejaz
left a comment
There was a problem hiding this comment.
Thanks for the quick turnaround. I re-checked bd9e2f8 against the gateway and chart code on main, and every AI Gateway point is addressed accurately. That includes the new includeSubjectClaims row: subject.claims is a string-to-string map, so only string-valued claims are sent. Leaving the other five extraHooks fields out for now makes sense to me. LGTM from the hooks side.

Description
Adds a how-to page for each gateway's policy webhooks, so operators can send requests to their own policy service.
connector-gateway/policy-webhooks):connector-gateway.enterpriseConfig.policyWebhooks: validating and mutating webhooks,match.toolsscoping, failure policy, TLS, and HMAC signing.pkg/webhookrather than repeating them, and lists only where the gateway's requests differ.ai-gateway/policy-webhooks):request.receivedandresponse.completed, plus required and observation webhooks, and the order they run in after the built-in checks.ai-gateway-v2.extraHooks:caBundleandtokenProjectionfor receiver trust,lifecycle.completionHookTimeout, and failure policy and retries.WebhookReviewrequest and response. Request bodies and usage are passed through as the provider sent them, so the page points receiver authors to each provider's API reference rather than documenting provider formats.Type of change
Related issues/PRs
extraHooks)Submitter checklist
Content and formatting
Navigation
sidebars.ts) updated for added, deleted, reordered, or renamed filesvercel.jsonfor moved, renamed, or deleted pages (i.e., if the URL slug changed)Reviewer checklist
Content
🤖 Generated with Claude Code