docs(langgraph): add Vaultak runtime security integration guide#4213
docs(langgraph): add Vaultak runtime security integration guide#4213Samuel Oladji (samueloladji-beep) wants to merge 4 commits into
Conversation
Adds a new page covering how to integrate Vaultak with LangGraph via the standard LangChain callback system (VaultakCallbackHandler). Every tool call is risk-scored before execution and PII is masked in outputs. - src/oss/langgraph/vaultak.mdx — integration guide with: - prebuilt create_react_agent example - custom StateGraph workflow example - per-invocation config example - configuration table and event-coverage table - src/docs.json — adds oss/python/langgraph/vaultak to the Production nav group after the observability page Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Thanks for opening a docs PR, Samuel Oladji (@samueloladji-beep)! When it's ready for review, please add the relevant reviewers:
|
|
Naomi Pentrel (@npentrel) Lauren Hirata Singh (@lnhsingh) Mason Daugherty (@mdrxy) — ready for review. This adds a Vaultak runtime security integration guide to the LangGraph Production section. |
Vale flagged 3 DashesSpaces violations at lines 11, 14, and 15. Replace ' — ' with '—' throughout prose (code block on line 135 is exempt). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
| @@ -0,0 +1,197 @@ | |||
| --- | |||
| title: Vaultak Runtime Security | |||
There was a problem hiding this comment.
We do not include third-party integration guides in our main docs set. Please remove this page and move the content into the providers page
…feedback Per @lnhsingh: third-party integration guides belong in the providers page, not as standalone pages in the main docs set. Merged all LangGraph-specific content (ReAct agent, StateGraph, config reference, monitoring table) into the existing providers/vaultak.mdx and removed the standalone langgraph/vaultak.mdx page and its docs.json entry. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Thanks for the review Lauren Hirata Singh (@lnhsingh) — makes sense, happy to follow the convention. I've moved all the LangGraph content (prebuilt ReAct agent, StateGraph workflow, config reference, and monitoring events table) into the existing providers page ( |
Summary
src/oss/langgraph/vaultak.mdx— a new integration guide in the LangGraph Production section covering how to wire Vaultak runtime security into LangGraph agents and StateGraph workflows.src/docs.jsonto addoss/python/langgraph/vaultakto the Production nav group, directly after the existing Observability page.Integration pattern
VaultakCallbackHandlerextends LangChain'sBaseCallbackHandler, so it plugs into LangGraph via the standardconfigdict with zero graph rewrites:Every tool call is risk-scored (0–10) before execution. Calls above the threshold raise an exception to halt the graph. Tool outputs are scanned for PII before they reach the next node.
Page contents
create_react_agentexample with two realistic toolsStateGraphworkflow example withToolNodeTest plan
/oss/python/langgraph/vaultakwithout errors<CodeGroup>, Python snippets)🤖 Generated with Claude Code