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

Abierto
#14,455 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
ai, documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

.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.

Lenguaje dominante
C#
Estrellas
28.8k
Forks
4.9k
Merge medio
2 d 17 h
PR fusionados (30 d)
48

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/semantic-kernel

Todos los issues de microsoft/semantic-kernel

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.