Check before action
Review a declared proposed AI-agent tool, API, webhook or workflow connection through the bounded, read-only MCP surface. Compatibility is not authority.
Guide 09 // Choosing the boundary
CHECK THE HAND-OFF. THEN OPERATE THE ROUTE.
A proposed connection and an event-delivery path are related—but they answer different operational questions.
01 // before action
Agent Preflight asks: do the declared parts fit?
AI-agent tools, APIs and webhook consumers can fail at the hand-off because a field is missing, an output has no declared consumer, formats differ, or an assumed adapter is not present. Agent Preflight keeps that first question bounded: inspect the declared connection before action.
Its current controlled-pilot boundary is account-scoped and read-only. It returns a redacted compatibility finding and a next action for human review; it does not contact arbitrary endpoints, change the workflow or grant permission to run it.
QUESTION
Does the proposed connection fit?
Check the declared producer, consumer, inputs, outputs, format and limits before a downstream system is asked to act.
QUESTION
How should approved events travel?
Delivery infrastructure concerns receiving, routing, delivering, retrying and observing events after a team has chosen an approved route.
02 // during delivery
Delivery infrastructure asks: how should events move and be observed?
Webhook delivery infrastructure is concerned with the operational path for events after a route has been approved: the destination, delivery controls, retries, traffic behaviour and the evidence needed to operate that route.
That is a broader category than a compatibility review. A delivery platform does not, by itself, decide whether an entire proposed AI-agent or tool connection is compatible or permitted.
03 // where Ingress Shield fits today
TWO COMPLEMENTARY SURFACES. ONE DELIBERATE BOUNDARY.
Protect a declared route
Protect and observe declared webhook traffic on a reviewed route. It is not positioned here as general-purpose delivery infrastructure or a replacement for one.
Keep the decision explicit
A team still reviews scope, data boundary, destination and any authority needed to take the next action.
YOU MAY NEED BOTH QUESTIONS.
First establish whether the declared connection is sufficiently understood for review. Then operate an approved route under the delivery controls appropriate to that system. Neither step makes an agent autonomous or removes human responsibility for authority and sensitive data. Ingress Shield is not a replacement for a webhook delivery platform, an integration platform or a production change-control process.