.Net: samples: add prompt-injection + tool-call hardening examples (filters)#13519
Open
aeris-systems wants to merge 1 commit intomicrosoft:mainfrom
Open
.Net: samples: add prompt-injection + tool-call hardening examples (filters)#13519aeris-systems wants to merge 1 commit intomicrosoft:mainfrom
aeris-systems wants to merge 1 commit intomicrosoft:mainfrom
Conversation
f93108c to
db30a2b
Compare
Author
|
@microsoft-github-policy-service agree company="Aeris Systems" |
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.
Draft: PR description (Semantic Kernel sample: prompt audit + tool gating)
Summary
Adds a small sample showing how to build a pre-validation sensor pipeline in Semantic Kernel using:
IPromptRenderFilterfor prompt audit + preflight scanningIAutoFunctionInvocationFilterfor tool gating (fail-closed for high-risk operations)Motivation
Teams are increasingly running SK agents against untrusted sources (web pages, PDFs, email, issue comments). The dominant practical risk is tool-output injection (malicious content steering the agent to exfiltrate secrets or invoke dangerous tools). The sample demonstrates a pragmatic mitigation pattern without changing SK core.
What’s included
Notes
Testing
dotnet testfor the sample project