docs: add guarded agent memory cookbook - #313
Open
vgudur-dev wants to merge 1 commit into
Open
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
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
1 participant
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.
Summary
This adds a focused, no-API-key notebook showing a guarded durable-memory boundary for Haystack agents. A benign external observation reaches Haystack's
InMemoryDocumentStoreonly after inspection by OWASP Agent Memory Guard (AMG). A representative indirect prompt-injection payload is blocked beforewrite_documents()is called, and the resulting security event remains available for logging or investigation.The accompanying
index.tomlentry categorizes the notebook underAgents,Memory, andGuardrails.Validation
The notebook scenario was exercised against public
haystack-ai==3.0.0andagent-memory-guard==0.3.0. It confirms that a benign observation persists, while the poisoned tool-output fixture raises AMG's strict-policy violation, emits aprompt_injectionevent withEXTERNAL_TOOLprovenance, and never reaches the document store.Scope
This is a small, deterministic example notebook. It uses Haystack's in-memory document store, requires no model provider or API key, and does not claim complete agent-security coverage.