cloud-audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUD_AUDIT_REGIONS | No | Comma-separated list of AWS regions to scan, or 'all'. Example: 'eu-central-1,eu-west-1'. | |
| CLOUD_AUDIT_ROLE_ARN | No | IAM role ARN to assume for cross-account scanning. Example: 'arn:aws:iam::123456789012:role/auditor'. | |
| CLOUD_AUDIT_MIN_SEVERITY | No | Minimum severity filter for findings. Example: 'high'. | |
| CLOUD_AUDIT_EXCLUDE_CHECKS | No | Comma-separated list of check IDs to skip. Example: 'aws-eip-001,aws-iam-001'. |
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 |
|---|---|
| scan_awsA | Run an AWS security scan and return a summary. Scans your AWS account for security misconfigurations, detects attack chains, and estimates breach cost risk. Args: profile: AWS CLI profile name (default: "default") regions: Comma-separated AWS regions to scan (default: profile region) min_severity: Minimum finding severity: critical, high, medium, low |
| get_findingsA | Get findings from the last scan, optionally filtered. Each finding includes check ID, severity, resource, description, and estimated breach cost. Args: severity: Filter by severity (critical, high, medium, low) service: Filter by AWS service prefix (e.g. "iam", "s3", "ec2", "vpc") limit: Maximum number of findings to return (default: 20) |
| get_attack_chainsA | Get all detected attack chains from the last scan. Attack chains are correlated findings that form exploitable attack paths. Each chain includes a narrative, priority fix, and breach cost estimate. |
| get_remediationA | Get remediation details (CLI command + Terraform code) for a specific check. Returns copy-paste ready AWS CLI command and Terraform HCL snippet to fix the finding. Args: check_id: The check ID (e.g. "aws-iam-001", "aws-s3-001", "aws-vpc-002") |
| get_health_scoreA | Get the current health score and risk exposure summary. Returns the 0-100 health score, finding counts by severity, attack chain count, and total estimated risk exposure in USD. |
| list_checksA | List all available security checks (no AWS credentials needed). Returns check IDs with their categories and services. |
| get_agent_blastA | What can a hijacked AI agent reach in this AWS account? For every Bedrock Agent, AgentCore runtime, gateway or sandbox found by the
last scan (or the one matching |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clear, distinct role: scanning, listing checks, retrieving findings, health scores, attack chains, remediation, and agent blast radius. No two tools overlap in purpose; even get_health_score and get_findings differ (summary vs. detailed list).
All tools follow a consistent verb_noun pattern: scan_aws, list_checks, get_findings, get_health_score, get_attack_chains, get_remediation, get_agent_blast. The verbs (scan, list, get) are used predictably, and the nouns clearly indicate the resource.
Seven tools is ideal for the domain of AWS security scanning: they cover the entire workflow from initiating a scan to viewing results, details, and remediation. Each tool is necessary and there is no bloat.
The tool set covers the full lifecycle: scan, list checks, get findings, get health score, get attack chains, get remediation, and even a specialized agent blast tool. The only minor gap is that there is no direct tool to initiate a specific check or re-scan a particular resource, but the existing tools allow agents to achieve the core goals.