feat(integrations): add phase 3 agent framework adapters - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds Phase 3 agent-framework integrations from MCP_RUNTIME_INTEGRATIONS_PRD.md:
Also adds shared agent security primitives for agent input/output scanning, unsafe handoff detection, role drift heuristics, cross-agent instruction smuggling heuristics, callable tool wrapping, optional package extras, docs, examples, and tests.
Why
Phase 1 established common runtime primitives and Phase 2 added LangChain MCP + LlamaIndex wrappers. Phase 3 extends the same security contract to agent-framework runtimes so ProofLayer can inspect agent inputs, outputs, tool calls, and handoff/delegation messages without changing each framework's native invocation flow.
Verification
Notes
Optional framework dependencies stay out of the base import path. The adapters use dependency-light proxies and fake-runtime tests so base CI remains stable while customers can install framework-specific extras when needed.