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

Open
#14,455 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
ai, documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
C#
Stars
28.8k
Forks
4.9k
Avg merge
2d 17h
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/semantic-kernel

All issues in microsoft/semantic-kernel

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.