Python: Integration: AffixIO host-side attestation for tool/plugin execution (IFunctionInvocationFilter)

Aperta
#14,455 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
ai, documentation

Direzione di ricerca

Start by reading the existing FunctionInvocationApproval demo under dotnet/samples/Demos/ and the IFunctionInvocationFilter documentation. The issue does not identify a target file or settle whether the contribution belongs in Semantic Kernel or Agent Framework, so get maintainer guidance before starting. Done means an approved documentation mention or minimal sample shows host-side approval before a privileged call and makes clear that the attestation is about the action, not the person's identity.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

.NET python triage

Summary

Proposal to document (and optionally sample) AffixIO as a host-side approval/attestation layer around Semantic Kernel tool and plugin execution, using the existing IFunctionInvocationFilter / function-invocation approval path.

AffixIO proves a host-side action completed (signed yes/no). It is not identity, age, or KYC. PII stays on the host.

Why this fits SK

SK already has:

  • IFunctionInvocationFilter for intercepting kernel function calls
  • the FunctionInvocationApproval demo sample under dotnet/samples/Demos/

AffixIO sits in that same place: gate privileged plugin/tool calls (secret use, remediations, admin actions) on the host before they run, then emit a signed yes/no attestation that the gate completed.

This is useful for agent orchestration where an LLM can select tools, but the enterprise needs a host-side proof that a human or policy gate actually approved the privileged call.

Minimal integration shape (no full middleware wrap)

  1. Install:
npm i affixio
# optional local MCP (stdio)
npm i @affixio/[email protected]
  1. In an IFunctionInvocationFilter (or Python equivalent filter), before invoking a privileged function:
  • call AffixIO to require host-side approval for that action
  • proceed only on signed yes
  • optionally attach the attestation id/result to logs/traces
  1. Keep AffixIO out of model prompts and out of PII paths. It attests the action, not the person.

Docs / sample ask

Happy to contribute a minimal sample (filter + AffixIO call) if maintainers want it under samples/docs. Not proposing a full AffixIO SDK wrap inside this repo.

Noting the README migration notice toward Microsoft Agent Framework; same filter/approval pattern should map there too. Filing here because SK still has the live filter APIs and approval demo.

Links

Ask

  1. Is an AffixIO mention or minimal sample under filters/approval docs welcome?
  2. Preferred target: Semantic Kernel samples, or Agent Framework equivalents?

Happy to follow maintainer guidance before any PR.

Lingua principale
C#
Stelle
28.8k
Fork
4.9k
Merge medio
2g 17h
PR unite (30g)
48

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/semantic-kernel

Tutte le issue di microsoft/semantic-kernel

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.