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
} |
| experimental | {} |
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. |
| checkA | Check a specific package for known CVEs before installing. |
| intel_lookupA | Look up one advisory from the local threat-intel database. |
| exposure_pathsA | Return ranked ExposurePath JSON for headless security agents. |
| 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 | Get OWASP LLM Top 10 / OWASP MCP Top 10 / MITRE ATLAS / NIST AI RMF compliance posture. |
| remediateA | Generate a remediation plan for vulnerabilities in your AI agent setup. |
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
scan and generate_sbom both extract dependencies but differ in output (AI-BOM vs SBOM); compliance and policy_check both evaluate security posture but one maps to frameworks and the other enforces custom rules. Most tools have clearly distinct purposes, though some overlap in the underlying scanning could confuse an agent.
Names mix single verbs (scan, check, remediate), nouns (compliance, exposure_paths), and verb_noun compounds (generate_sbom, policy_check, intel_lookup). The inconsistency in verb style and structure reduces predictability, though all are readable.
8 tools is well-scoped for an AI supply chain security server, covering scanning, checking, compliance, SBOM generation, policy, remediation, intel, and exposure paths. No tool feels redundant or unnecessary.
Core lifecycle is covered: scan, check, generate_sbom, compliance, policy_check, remediate, plus intel_lookup and exposure_paths. Missing a dedicated 'list past scans' or policy management tool, but scan's result_id paging mitigates; minor gaps only.