Local invoke adapter / offline ToolCall fixture
LangChain
Choose an accessible execution boundary, start in observe mode, then verify detector readiness before relying on policy decisions.
Platform surfaces
- Supported locally
- toolAdapter preserves name, description and schema and guards the actual invoke / ToolCall executor, retaining tool IDs and execution configuration.
- Planned
- Broader LangGraph and framework batch/stream qualification remains pending.
- Unsupported / unqualified
- The invoke adapter does not qualify batch/stream paths. Class ToolMessage response replacement is unavailable; original outcomes survive with a bypass.
Observe before enabling repair.
- Build the unpublished local package. Select the supported adapter and explicitly identify write or ambiguous operations; generic callables default to read.
- Await readiness and supply scoped detection selections. Detection is off until you configure it; watch warming and bypass events.
- Review request/response evidence in observe. Enabling repair requires an explicit trusted engine, confidence and verification; changing mode does not add a repair implementation.
- Review completed dispatch and idempotency evidence before any caller-authorized replay. A response halt cannot roll back an upstream action.
Node Fetch inspection requires complete JSON with known content length and a bounded copy. Chunked, unknown-length and non-JSON bodies skip inspection; incoming Node streams are not consumed or repaired.
Protection, evidence and deployment prerequisites →Adoption order / Pipedream → LangChain → Nango → Mastra
Compare all platform surfaces →