Agent Q
Reviews GitHub pull requests (added lines), commits and whole repositories through the GitHub API, returning policy findings with rule identifiers, severities and file/line locations, plus a verdict of APPROVE, COMMENT or CHANGES REQUESTED. Optionally accepts a caller-supplied GitHub token to raise rate limits and reach private repositories, and can list the repositories of an account.
Provides a drop-in workflow template that runs Agent Q on every pull request using the job's own GITHUB_TOKEN, keeps a single review comment up to date, and fails the job when the verdict is CHANGES REQUESTED.
Provides a Copilot custom agent definition that can be copied into a repository's .github/agents/ directory, making Agent Q's review tools available in that repository's Copilot agents list.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Intent-Auditable Trust Object V2
This repository provides iato, a C# (.NET 8) command line tool that configures Debian hosts to authenticate Microsoft Entra ID users through the SSSD identity provider (idp) back end. SSSD reads users and groups from Microsoft Graph, signs users in with the OAuth 2.0 Device Authorization Grant (RFC 8628), and derives consistent POSIX UIDs and GIDs from Entra object IDs, so no ID mapping is managed by hand. It is not an identity provider, a directory service or a replacement for SSSD; it renders, checks and installs SSSD configuration and verifies the result.
The key words MUST, MUST NOT, SHALL, SHOULD and MAY in this document are to be interpreted as described in BCP 14 (RFC 2119 and RFC 8174).
Contents
Related MCP server: shipcheck-mcp
Key features
iato has four parts. Each one is a subcommand that runs against Microsoft Graph, a configuration file or a Debian host, and each states what checks it.
# | Feature | What runs | Checked by |
1 |
| xUnit test of the Graph request body; not run in CI, which has no tenant | |
2 |
| xUnit tests; | |
3 |
| xUnit tests; | |
4 |
|
|
1. Entra ID app registration
Creating the Entra ID app registration through Microsoft Graph (
iato register-app).An Entra ID app registration gives SSSD application permissions to read users and group membership, and allows public client flows for device code sign in.
Graph permissions requested: application
User.Read.AllandGroupMember.Read.All; delegatedopenid,profileandemail. Admin consent is granted for both.The client secret is written to
entra-app.envwith mode 0600. The token is taken fromIATO_GRAPH_TOKENoraz account get-access-token.
2. Rendering of sssd.conf for the idp domain
Rendering
sssd.conffor theidpdomain (iato render).The template
sssd/sssd.confis compiled into the binary, so hosts need nothing else on disk.Missing or multi line values are rejected before any file is written, and the output file is created with mode 0600.
3. Configuration and host checks
Checking
sssd.conffor theidpdomain (iato check): placeholders, duplicate keys, requiredidpsettings, https endpoints, idmap range andconfig_file_version.--hostalso checks the installed SSSD version (2.11.0 or later), the presence oflibsss_idp.soand the file mode.The checks do not depend on the
sssctlrule set, which can lag new back ends.
4. Host installation and verification
Installing and enabling SSSD,
pam_sssand the sshd drop in on Debian hosts (iato install).Verifying that a user resolves and may log in (
iato verify).iato installstarts SSSD only after the configuration and host checks pass.
Scope
Out of scope:
Distributions other than Debian.
SSSD versions earlier than 2.11.0, which have no
idpprovider.The OpenLDAP domain and Debian packaging, which are held on separate branches (see Branches).
Known limitations:
The ID mapping can, in rare cases, assign the same ID to two objects; only the first one resolved is available.
The client secret is the only credential type supported for this provider at present.
On Debian 12 and 13, SSSD packages are taken from Debian forky through an apt pin rather than from the installed release.
Planned work (not implemented):
A certificate credential in place of the client secret, once SSSD supports one for the
idpprovider (see Configuration).
Architecture
How it works
An Entra ID app registration gives SSSD application permissions to read users and group membership, and allows public client flows for device code sign in.
SSSD runs with
id_provider = idpandidp_type = entra_id.getentandidresolve Entra users and groups.At login,
pam_sssshows a verification URL and code. The user signs in on any browser, Conditional Access and MFA apply, and SSSD completes the login once Entra confirms.access_provider = simplelimits logins to one Entra group.
Components
admin workstation Microsoft Entra ID
----------------- ------------------
iato register-app ---- Graph v1.0 ----> app registration, service principal,
| app role assignments, admin consent,
v client secret
entra-app.env (0600)
|
v Debian host
+---------------------------------------------------------------+
| iato install / render / check --host |
| -> /etc/sssd/sssd.conf (root, 0600), [domain/entra] |
| -> apt pin to forky on bookworm and trixie |
| -> pam-auth-update (sss, mkhomedir), sshd drop in |
| |
| sssd (id_provider = idp) ---- token, Graph lookups ---------> | Entra ID, Graph
| pam_sss <- sshd (keyboard-interactive) |
| device code prompt ----- RFC 8628 device authorization --> | Entra ID
| iato verify -> sssctl, getent, id |
+---------------------------------------------------------------+References
Repository layout
Path | Purpose |
| The CLI (.NET 8) |
| xUnit tests for rendering, checks and the Graph request |
| Template for the |
| forky source and pin so only SSSD packages come from forky |
| sshd drop in enabling keyboard-interactive for the device code prompt |
| Figures used in this README and the text logs they were captured from |
| Build, test, then |
| Produces the figures in this README on an Xvfb display |
Branches
Branch | Holds |
| The |
|
|
|
|
History
This repository was named agent-q until v2. Versions up to v0.3.0 were Agent Q, a pull request reviewer on Cloudflare Workers and Supabase. That code remains at the v0.3.0 tag and release. v1.0.0 was the first release of the SSSD project.
Requirements
Item | Detail |
SSSD | 2.11.0 or later MUST be installed. Debian 12 ships 2.8.2 and Debian 13 ships 2.10.1, so this repository pins SSSD packages from Debian forky (2.13). Debian forky and sid ship a suitable version as is. |
Packages |
|
Entra ID | Rights to create an app registration and grant admin consent |
Graph permissions | Application: |
Build | .NET 8 SDK, only when building from source |
The released binary is self contained, so hosts do not need a .NET runtime. Templates are compiled into it.
Build
Build from source
dotnet test
dotnet publish src/Iato -c Release -r linux-x64 --self-contained -p:PublishSingleFile=true -o outFigure 2 shows dotnet build -c Release and Figure 3 shows dotnet test on the CI runner.
Install from a release
Releases are cut from the release/2.x branch. Each one attaches iato_<version>_amd64.deb, iato_<version>_arm64.deb, standalone iato-linux-x64 and iato-linux-arm64 binaries, a source tarball and SHA256SUMS. Downloads SHOULD be checked against SHA256SUMS before installation.
V=2.0.0
curl -LO https://github.com/whatheheckisthis/Intent-Auditable-Trust-Object-V2/releases/download/v$V/iato_${V}_amd64.deb
curl -LO https://github.com/whatheheckisthis/Intent-Auditable-Trust-Object-V2/releases/download/v$V/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
sudo apt install ./iato_${V}_amd64.debUsage
iato register-app --name sssd-debian-hosts --out entra-app.env # once per tenant
sudo iato install --env entra-app.env --group linux-admins # on each host
iato verify alex@contoso.onmicrosoft.comiato register-app runs once per tenant. iato install runs on each host and MUST run as root. On Debian 12 and 13, iato install adds the forky pin before installing SSSD.
Command | Behaviour |
| Creates the Entra app registration through Microsoft Graph, grants admin consent, and writes |
| Renders |
| Checks a config: placeholders, duplicate keys, required |
| Pins SSSD from forky where needed, installs packages, writes the config, enables |
| Runs |
| Prints the tool version. |
The built in help is shown in Figure 1.
Walkthrough
The steps below follow one tenant and one host from app registration to an SSH sign in. Steps 2, 3 and 7 have captured figures from the CI runner. Steps 1, 4, 5 and 6 require a live Entra ID tenant or a Debian host running systemd, which CI does not provide, so no figure is published for them; see Figures.
Register the Entra ID app once per tenant. The client secret is written to a file only the owner can read. Without a Graph token,
iato register-appstops before any request is sent (Figure 1).Render
sssd.conffor theidpdomain and check it before it reaches a host (Figures 4 and 5).iato checkstops a broken configuration: an unrendered placeholder, a key SSSD 2.13 rejects and endpoints that are not https (Figure 5).Install on a Debian 13 host. SSSD packages are pinned from forky, and SSSD starts only after the host checks pass. Figure 7 shows the host check that fails on Debian 13 without the pin, and Figure 6 the same check passing against SSSD from forky.
Verify that an Entra ID user resolves to a POSIX account and passes the access check for the allowed group.
The user signs in over SSH. SSSD shows a device code, the user completes sign in on any browser with MFA and Conditional Access, and the session opens.
The unit tests cover rendering, checks and the Graph request (Figure 3).
Configuration
sssd/sssd.confis the template for theidpdomain.iato renderandiato installfill it fromentra-app.envand the--groupvalue.apt/holds the forky source and pin so that only SSSD packages come from forky.ssh/holds the sshd drop in that enables keyboard-interactive authentication for the device code prompt.The client secret grants tenant wide read of users and group membership. It MUST be stored only in
/etc/sssd/sssd.conf(root, 0600). A certificate credential SHOULD be preferred once SSSD supports one for this provider.cache_credentials = false: every login goes to Entra, so revoked accounts lose access at the next sign in.idmap_range_*values MUST be identical across hosts.
Verification and testing
dotnet testruns the xUnit tests intests/Iato.Tests/, which cover rendering, checks and the Graph request..github/workflows/ci.ymlbuilds and tests on each push and pull request, then runsiato check --hostagainst SSSD in a Debian forky container. Continuous integration does not cover Debian 12, Debian 13 or sid hosts..github/workflows/captures.ymlrepeats the build and tests on anubuntu-24.04runner and captures the figures in this README.On a configured host,
iato verify <user@tenant>MAY be used to confirm that a user resolves and may log in.
Test results
The captures run of commit 57bda29 on an ubuntu-24.04 runner reported the following (Figures 2 and 3; logs in docs/screenshots/02-dotnet-build.log and docs/screenshots/03-dotnet-test.log).
Check | Result |
| Build succeeded: 0 errors, 1 warning (xUnit analyzer |
| 10 tests in total, 10 passed, none failed |
|
|
| 2 errors, exit status 1, as intended |
The ten tests, in the order the runner reported them:
Test | Covers |
| Debian package version parsing used by |
| Rejected key and duplicate key detection |
| Multi line values cannot inject settings |
| Rendering stops when a value is missing |
|
|
| The rendered template has no placeholders and no errors |
| Output files are created with mode 0600 |
| The Graph application body requests the two application roles and allows public client flows |
Figures
All figures are produced by .github/workflows/captures.yml on an ubuntu-24.04 runner, run 44444112722 of commit 57bda29. Each figure is an xterm window on an Xvfb display running the commands it shows, captured with ImageMagick import -window; the only edit is cropping of empty terminal space. No figure is drawn by hand. The text that each terminal printed is kept beside the image as a .log file in docs/screenshots/. The Entra identifiers and the client secret are the same placeholders used by ci.yml (00000000-... tenant, 11111111-... client, ci-placeholder), and no tenant is contacted. Select any figure to open it at full resolution.
Figure | Subject | Tool | Source |
1 |
|
|
|
2 | Release build | .NET SDK 11.0.100, MSBuild |
|
3 | Unit tests |
|
|
4 | Rendered |
|
|
5 | Configuration check on a valid and a broken file |
|
|
6 | Host check against SSSD 2.13.1 in Debian forky |
|
|
7 | Host check against SSSD 2.10.1 in Debian 13 |
|
|
The following are not captured, because they need resources that CI does not have: iato register-app against a real tenant (it requires a Graph token with rights to create an app registration), iato install (it requires a Debian host running systemd), iato verify (it requires a running SSSD joined to a tenant), and the SSSD device code prompt at SSH login (it is printed by pam_sss after a live device authorization request to Entra ID). The Graph request body is covered by a unit test instead (Figure 3).
Command line
Build and tests
Configuration
Host checks
Security
Security reporting and commit signature verification are described in SECURITY.md; the maintainer signing key is published in KEYS.asc.
License
This project is licensed under the Apache License, Version 2.0. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
IaC, CI and dependency security review for coding agents: local scan CLI plus hosted OAuth MCP.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Hosted MCP server for pre-action AI governance verdicts, model routing, and evidence verification.
41Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Related MCP Servers
- AlicenseCqualityDmaintenanceA policy-aware MCP server for GitHub and GitHub Actions that enables safe AI-assisted infrastructure workflows—inspecting repositories, preparing branches and pull requests, and constrained remote mutations behind explicit preview-bound approval tokens.18MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.63 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run security and code review on pull requests and diffs, exposing review_pr and review_diff capabilities with local-first analyzers and LLM explanations.2MIT
- AlicenseBqualityCmaintenanceEnables automated pull request review, security vulnerability analysis, and code quality improvement suggestions through any MCP client.323 npmMIT