agent-bom
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scanA | Run a full AI supply chain security scan and return an AI-BOM. Point it at a target with one of:
• project_path — a local project / repo directory ("scan this repo";
must be inside home or AGENT_BOM_MCP_WORKSPACE_ROOTS)
• repo_url — a public git repo URL (cloned + scanned, no checkout)
• config_path — a local MCP-config directory
• image — a Docker image
• sbom_path — an existing CycloneDX/SPDX SBOM
• package — a single package or MCP launch command (pair it with
It extracts package dependencies, looks up CVEs (online via OSV.dev and advisory sources unless offline mode is requested or configured), assesses config security (credential exposure, tool access), computes blast radius, and returns structured results. Scanning is fully static and read-only — repository and image contents are parsed, never executed. Returns: JSON. By default a bounded summary: counts (packages, agents, findings by severity/category), top findings, affected paths, and a result_id. Page any full-fidelity section with scan(result_id=..., section='findings', offset=0, limit=25). An incomplete scan (e.g. vulnerability source unavailable) is returned as an error result whose body is still JSON. |
| checkA | Check a specific package for known CVEs before installing. |
| intel_lookupA | Look up one advisory from the local threat-intel database. |
| policy_checkA | Evaluate a security policy against current scan results. |
| generate_sbomA | Generate a Software Bill of Materials (SBOM) for your AI agent setup. |
| complianceA | Return compliance posture with its source: the tenant's persisted evidence, or a labelled local scan. |
| remediateA | Generate a remediation plan for vulnerabilities in your AI agent setup. |
| exposure_pathsA | Return the attack-path queue in the dashboard's order, with why each path ranks where it does. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| quick-audit | Run a complete security audit of your AI agent setup |
| pre-install-check | Check an MCP server package for vulnerabilities before installing |
| remediation-plan | Draft a human-reviewed remediation plan without modifying files |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| profiles_resource | Task profiles and startup commands; no tool schemas or credentials |
| policy_template_resource | Get a default security policy template for agent-bom. Returns a ready-to-use policy with common rules: block critical CVEs, flag CISA KEV entries, warn on unverified servers, and limit credential exposure. |
| tool_metrics_resource | Return bounded MCP tool execution metrics for observability. |
| framework_controls_resource | Summarize framework coverage and the evidence surfaces behind each claim. |
TDQS
Scored across 8 tools
Most tools target clearly distinct outputs: scan (full assessment), check (single package CVE lookup), compliance, policy_check, remediate, exposure_paths, intel_lookup. The main confusion is between scan and generate_sbom, since scan already returns an 'AI-BOM' and affected paths while generate_sbom returns a standards-compliant SBOM, plus mild overlap between check (OSV package CVEs) and intel_lookup (local advisories). Descriptions help but an agent could easily pick the wrong one for a 'give me an SBOM' request.
Names are all snake_case (one word or two), so character style is uniform, but the verb/noun convention is mixed: bare verbs (scan, check, remediate), noun phrases (exposure_paths, compliance), and odd compounds (intel_lookup, policy_check). Readable in aggregate but not a predictable verb_noun pattern.
Eight tools is a sensible scope for a supply-chain security server. Several tools (scan, remediation, policy_check, compliance, generate_sbom) internally re-run the same scan, so there is a bit of functional redundancy, but none feels wholly unjustified.
Covers discovery/scanning, package CVE check, SBOM export, compliance, attack-path ranking, policy gating, and remediation — a strong lifecycle. Gaps remain: no scan history/session listing, no diff/compare between scans, no finding suppression/waiver or credential inventory tool, and result paging is only reachable through scan.