@aaa-sentinel/mcp-server 0.8.0 → 0.9.0

package/README.md

@@ -29,7 +29,7 @@ dashboard you have to remember to visit.
   only those; the scopes you leave out are simply not reachable from the assistant.
 - A **Pro** plan or above: the API is not available on the free plan. Chargeback, cost anomalies,
   unit cost, managed clients and the agent need **Business**, and the security tools also need the
-  security add-on on the account — the table below says which.
+  risk and compliance add-on on the account — the table below says which.
 
 ## Configuration
 
@@ -107,13 +107,14 @@ status as plain JSON.
 | `get_dashboard` | `accountId?` | `dashboard:read` | Pro |
 | `get_cost_forecast` | `accountId` | `reports:read` | Pro |
 | `list_cost_anomalies` | `accountId?` | `reports:read` | Business |
-| `get_security_overview` | — | `security:read` | Pro + security add-on |
-| `get_security_score` | `accountId` | `security:read` | Pro + security add-on |
-| `list_security_findings` | `accountId`, `source?`, `category?` | `security:read` | Pro + security add-on |
-| `get_security_critical_changes` | `accountId` | `security:read` | Pro + security add-on |
-| `list_security_vulnerabilities` | `accountId` | `security:read` | Pro + security add-on |
-| `get_security_conformance` | `accountId` or `clientId` | `security:read` | Pro + security add-on |
-| `get_security_posture_history` | `accountId` or `clientId`, `days?` | `security:read` | Pro + security add-on |
+| `get_security_overview` | — | `security:read` | Pro + risk and compliance add-on |
+| `get_security_score` | `accountId` | `security:read` | Pro + risk and compliance add-on |
+| `list_security_findings` | `accountId`, `source?`, `category?` | `security:read` | Pro + risk and compliance add-on |
+| `get_security_critical_changes` | `accountId` | `security:read` | Pro + risk and compliance add-on |
+| `list_security_vulnerabilities` | `accountId` | `security:read` | Pro + risk and compliance add-on |
+| `get_security_tool_spend` | `accountId` | `security:read` | Pro + risk and compliance add-on |
+| `get_security_conformance` | `accountId` or `clientId` | `security:read` | Pro + risk and compliance add-on |
+| `get_security_posture_history` | `accountId` or `clientId`, `days?` | `security:read` | Pro + risk and compliance add-on |
 | `get_account` | `accountId` | `accounts:read` | Pro |
 | `get_account_monthly_costs` | `accountId` | `accounts:read` | Pro |
 | `get_cost_history` | `accountId` | `reports:read` | Pro |
@@ -165,14 +166,14 @@ not an outage yet), `down`, or `recovering` (still counted as down until the rec
 confirmed). The last result carries a reason code such as `timeout`, `status_mismatch` or
 `queue_dlq_not_empty`; the full list is in the API reference.
 
-The security tools need the security add-on enabled on the account (20 €/month per account).
+The security tools need the risk and compliance add-on enabled on the account (20 €/month per account).
 Without it they answer with `access: "teaser"` and no scan data, so the assistant can tell
 "not enabled" apart from "nothing found".
 
 ### Why there is nothing that writes
 
 There is no tool to approve a remediation, launch a playbook, stop an instance, start a security
-scan or enable the (billed) security add-on, and that is a
+scan or enable the (billed) risk and compliance add-on, and that is a
 decision rather than a gap. An MCP server with write access puts a model — with its own idea of
 what is convenient, and a prompt an attacker may have influenced — inside the path that changes
 your infrastructure. Execution stays in the product, where it is gated by approvals, dry runs and

package/dist/cli.js

@@ -6065,7 +6065,7 @@ function defineTool(def) {
 }
 var SAVINGS_TYPES = ["compute", "storage", "network", "database", "serverless", "governance"];
 var SECURITY_SOURCES = ["own", "corroborated", "securityhub", "guardduty", "defender", "scc"];
-var SECURITY_CATEGORIES = ["security_network", "security_exposure", "security_encryption", "security_iam", "security_logging", "security_secrets"];
+var SECURITY_CATEGORIES = ["security_network", "security_exposure", "security_encryption", "security_iam", "security_logging", "security_secrets", "security_patching"];
 var AGENT_STATUSES = ["proposed", "pending_approval", "pending_second_approval", "approved", "executing", "completed", "failed", "cancelled", "expired"];
 var BillingPeriod = string2().regex(/^\d{4}-(0[1-9]|1[0-2])$/, "Use YYYY-MM");
 var ACCOUNT_ID = { type: "string", description: "Account identifier, as returned by list_accounts." };
@@ -6204,14 +6204,14 @@ var TOOLS = [
   // queda en la API y la app, no en un agente ajeno.
   defineTool({
     name: "get_security_overview",
-    description: 'Get the security posture of every cloud account: Score (0-100), band, findings by severity and attack chains. Accounts without the security add-on come back as access "teaser" with no data. Requires the security:read scope and the Pro plan or above.',
+    description: 'Get the security posture of every cloud account: Score (0-100), band, findings by severity and attack chains. Accounts without the risk and compliance add-on come back as access "teaser" with no data. Requires the security:read scope and the Pro plan or above.',
     inputSchema: { type: "object", properties: {} },
     argsSchema: object({}),
     handler: async (_args, config2) => apiGet("/v1/security/overview", void 0, config2)
   }),
   defineTool({
     name: "get_security_score",
-    description: "Get the security Score of the latest security scan of one account, with its coverage (which rules could not be evaluated and which permission was missing). Requires the security:read scope, the Pro plan and the security add-on on that account.",
+    description: "Get the security Score of the latest security scan of one account, with its coverage (which rules could not be evaluated and which permission was missing). Requires the security:read scope, the Pro plan and the risk and compliance add-on on that account.",
     inputSchema: {
       type: "object",
       properties: { accountId: { type: "string", description: "Account identifier, as returned by list_accounts." } },
@@ -6222,7 +6222,7 @@ var TOOLS = [
   }),
   defineTool({
     name: "list_security_findings",
-    description: 'List the security findings of the latest security scan of one account (up to 500, most severe first), with attack chains and a diff against the previous scan. Use category "security_iam" for the permissions view: effective administrators, unused identities, keys and service accounts, granted permissions that are not used, and assignments to deleted identities. Requires the security:read scope, the Pro plan and the security add-on on that account.',
+    description: 'List the security findings of the latest security scan of one account (up to 500, most severe first), with attack chains and a diff against the previous scan. Use category "security_iam" for the permissions view: effective administrators, unused identities, keys and service accounts, granted permissions that are not used, and assignments to deleted identities. Each finding may carry resourceCost, and the response exposedCost (what the account pays per month in resources with critical or high findings): both are estimates from the latest cost scan of at most 14 days (list price or what the resource was billed), in USD and approximate, absent when there is no cost data. Each finding may also carry attribution (the Owner, Team and CostCenter tags of its resource; unowned when its tags were read and it has neither Owner nor Team; absent when its tags were not read), and the response attributionSummary (findings and exposed cost by team and by cost center); critical findings without an owner come first among the critical ones. Requires the security:read scope, the Pro plan and the risk and compliance add-on on that account.',
     inputSchema: {
       type: "object",
       properties: {
@@ -6249,7 +6249,7 @@ var TOOLS = [
   }),
   defineTool({
     name: "get_security_critical_changes",
-    description: "List the critical configuration changes of the last 7 days in one account (up to 100, newest first), read from CloudTrail in AWS, the activity log in Azure or the Admin Activity audit logs in GCP: public bucket, storage or snapshot, remote admin open to the internet, logging turned off, root use, admin granted. Each comes with who made it and, for rule-backed changes, whether a re-check confirmed the risk. Accounts without the security add-on return supported false and an empty list. Requires the security:read scope and the Pro plan or above.",
+    description: "List the critical configuration changes of the last 7 days in one account (up to 100, newest first), read from CloudTrail in AWS, the activity log in Azure or the Admin Activity audit logs in GCP: public bucket, storage or snapshot, remote admin open to the internet, logging turned off, root use, admin granted. Each comes with who made it and, for rule-backed changes, whether a re-check confirmed the risk. Accounts without the risk and compliance add-on return supported false and an empty list. Requires the security:read scope and the Pro plan or above.",
     inputSchema: {
       type: "object",
       properties: { accountId: { type: "string", description: "Account identifier, as returned by list_accounts." } },
@@ -6260,7 +6260,7 @@ var TOOLS = [
   }),
   defineTool({
     name: "list_security_vulnerabilities",
-    description: "List the vulnerabilities (CVEs) that the cloud native scanner already found in one account (Amazon Inspector or ECR basic scanning, Microsoft Defender for Cloud, GCP Artifact Analysis and VM Manager), up to 200, highest priority first. Each one has the cloud severity and an effective severity that rises when the resource is exposed to the internet, has a known exploit or is unused according to a cost rule (low CPU is shown as context only). AAA Sentinel does not scan on its own: tools shows whether each scanner is active, absent or could not be read, truncated whether the cloud has more than the cap, and partial why the list may be incomplete (scanner missing in some regions or resource types listed in uncovered, failed reads, time budget, unreadable entries, expired rows). Amazon Inspector only sees image use on ECS and EKS: when the account has container Lambdas, App Runner services or images not in use there, uncovered.gaps says ecr_images_outside_ecs_eks and those images come last with imageInUse false. An account without the security add-on returns access teaser and an empty list, which does not mean it has no vulnerabilities. bySeverity counts the effective severity. Requires the security:read scope and the Pro plan or above.",
+    description: "List the vulnerabilities (CVEs) that the cloud native scanner already found in one account (Amazon Inspector or ECR basic scanning, Microsoft Defender for Cloud, GCP Artifact Analysis and VM Manager), up to 200, highest priority first. Each one has the cloud severity and an effective severity that rises when the resource is exposed to the internet, has a known exploit or is unused according to a cost rule (low CPU is shown as context only). AAA Sentinel does not scan on its own: tools shows whether each scanner is active, absent or could not be read, truncated whether the cloud has more than the cap, and partial why the list may be incomplete (scanner missing in some regions or resource types listed in uncovered, failed reads, time budget, unreadable entries, expired rows). Amazon Inspector only sees image use on ECS and EKS: when the account has container Lambdas, App Runner services or images not in use there, uncovered.gaps says ecr_images_outside_ecs_eks and those images come last with imageInUse false. An account without the risk and compliance add-on returns access teaser and an empty list, which does not mean it has no vulnerabilities. bySeverity counts the effective severity. Requires the security:read scope and the Pro plan or above.",
     inputSchema: {
       type: "object",
       properties: { accountId: { type: "string", description: "Account identifier, as returned by list_accounts." } },
@@ -6269,6 +6269,17 @@ var TOOLS = [
     argsSchema: object({ accountId: string2().min(1) }),
     handler: async ({ accountId }, config2) => apiGet("/v1/security/vulnerabilities", { accountId }, config2)
   }),
+  defineTool({
+    name: "get_security_tool_spend",
+    description: "Get what one account pays for the cloud's own security tools (AWS Security Hub, GuardDuty, Inspector, Config, WAF and CloudTrail; Microsoft Defender for Cloud and Azure WAF; GCP Security Command Center and Cloud Armor) this month so far and last month, and what AAA Sentinel does with each one: imports and deduplicates its findings, uses it as a data source, checks it, or does not use it for its diagnosis. Answers whether you pay twice for the same thing: overlap counts own findings the tool also reports (corroborated) and findings only the tool brings (importedOnly; capped means at least). Each tool has current and previous ({ spendUsd, costScannedAt }, null when that month has no real bill) and billing.current/previous carry totalSpendUsd (totalPartial when some tool has no amount). Amounts are in USD from the real bill of the latest cost scan of each month; spendUsd 0 means the bill read has no charge for that service, and null means it is not billed separately or its bill name is not confirmed and does not appear. state null means no state is available (no scan, an older scan, or a tool whose state is not read). CloudTrail is the whole service (management and data events together); Azure WAF (azurewaf) and Cloud Armor have no line of their own in the bill. On AWS the payer account sees the whole organization and on GCP the whole billing account (billing.scope). That AAA Sentinel does not use a tool does not mean it can be turned off. Requires the security:read scope, the Pro plan or above and the risk and compliance add-on on the account.",
+    inputSchema: {
+      type: "object",
+      properties: { accountId: { type: "string", description: "Account identifier, as returned by list_accounts." } },
+      required: ["accountId"]
+    },
+    argsSchema: object({ accountId: string2().min(1) }),
+    handler: async ({ accountId }, config2) => apiGet("/v1/security/tools", { accountId }, config2)
+  }),
   defineTool({
     name: "get_security_conformance",
     description: "Get CIS benchmark coverage for one account, or for every account of a managed client (clientId, Business plan). Pass exactly one of accountId or clientId. Requires the security:read scope, plus reports:read when using clientId.",
@@ -6286,7 +6297,7 @@ var TOOLS = [
   }),
   defineTool({
     name: "get_security_posture_history",
-    description: "Get how the security posture changed over 30, 90 or 365 days (default 90) for one account, or for every account with the security add-on of a managed client (clientId, Business plan, up to 20 accounts; omitted counts the rest). Returns points, one per UTC day (the last scan of that day: score, scored/total rules, open findings by severity, events), and summary: from/to (Score of the first and last point), resolved (distinct findings gone in a scan that fully evaluated their rule), opened (new, from rules already fully evaluated before), surfaced (new but not comparable: rule not fully evaluated before, or an external tool), unverified (gone without confirmation), meanFixDays by severity, comparable and notComparableReasons. When comparable is false, do not describe the Score change as the account getting better or worse. Points keep the Score computed each day, without discounting risks accepted later (acceptedRisks). Pass exactly one of accountId or clientId. Requires the security:read scope, plus reports:read when using clientId.",
+    description: "Get how the security posture changed over 30, 90 or 365 days (default 90) for one account, or for every account with the risk and compliance add-on of a managed client (clientId, Business plan, up to 20 accounts; omitted counts the rest). Returns points, one per UTC day (the last scan of that day: score, scored/total rules, open findings by severity, events), and summary: from/to (Score of the first and last point), resolved (distinct findings gone in a scan that fully evaluated their rule), opened (new, from rules already fully evaluated before), surfaced (new but not comparable: rule not fully evaluated before, or an external tool), unverified (gone without confirmation), meanFixDays by severity, comparable and notComparableReasons. When comparable is false, do not describe the Score change as the account getting better or worse. Points keep the Score computed each day, without discounting risks accepted later (acceptedRisks). Each point also has exposedCost (monthly spend on resources with critical or high findings, or null without cost data), and the summary has exposedCost (from/to) and comboSavings (monthly spend no longer paid after exposed unused resources were deleted, counted only when the resource stopped existing in a scan that fully evaluated its rules, at the last known amount of each resource). Each point uses the cost scan that was current when that security scan ran; amounts are estimates (list price or what the resource was billed), in USD and approximate. Pass exactly one of accountId or clientId. Requires the security:read scope, plus reports:read when using clientId.",
     inputSchema: {
       type: "object",
       properties: {
@@ -6640,7 +6651,7 @@ function findTool(name) {
 
 // src/protocol.ts
 var SERVER_NAME = "aaa-sentinel-mcp";
-var SERVER_VERSION = "0.8.0";
+var SERVER_VERSION = "0.9.0";
 var SUPPORTED_PROTOCOL_VERSIONS = ["2025-06-18", "2025-03-26", "2024-11-05"];
 var PARSE_ERROR = -32700;
 var INVALID_REQUEST = -32600;

package/package.json

@@ -1,45 +1,45 @@
-{
-  "name": "@aaa-sentinel/mcp-server",
-  "version": "0.8.0",
-  "description": "Read-only MCP server for AAA Sentinel: query cloud costs, savings, security posture, AI spend, uptime monitoring, the remediation agent and managed clients from an AI assistant",
-  "license": "MIT",
-  "type": "module",
-  "bin": {
-    "aaa-sentinel-mcp": "dist/cli.js"
-  },
-  "files": [
-    "dist"
-  ],
-  "keywords": [
-    "mcp",
-    "modelcontextprotocol",
-    "finops",
-    "cost",
-    "monitoring",
-    "uptime",
-    "security",
-    "ai-spend"
-  ],
-  "publishConfig": {
-    "access": "public"
-  },
-  "homepage": "https://app.aaa-sentinel.com/developer/docs#mcp",
-  "bugs": {
-    "url": "https://app.aaa-sentinel.com/contact"
-  },
-  "engines": {
-    "node": ">=20"
-  },
-  "scripts": {
-    "build": "esbuild src/cli.ts --bundle --platform=node --format=esm --target=node20 --outfile=dist/cli.js",
-    "prepublishOnly": "npm run build",
-    "test": "vitest run"
-  },
-  "devDependencies": {
-    "@types/node": "^22.0.0",
-    "esbuild": "^0.24.0",
-    "typescript": "^5.7.0",
-    "vitest": "^3.2.0",
-    "zod": "^4.6.7"
-  }
-}
+{
+  "name": "@aaa-sentinel/mcp-server",
+  "version": "0.9.0",
+  "description": "Read-only MCP server for AAA Sentinel: query cloud costs, savings, security posture, AI spend, uptime monitoring, the remediation agent and managed clients from an AI assistant",
+  "license": "MIT",
+  "type": "module",
+  "bin": {
+    "aaa-sentinel-mcp": "dist/cli.js"
+  },
+  "files": [
+    "dist"
+  ],
+  "keywords": [
+    "mcp",
+    "modelcontextprotocol",
+    "finops",
+    "cost",
+    "monitoring",
+    "uptime",
+    "security",
+    "ai-spend"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "homepage": "https://app.aaa-sentinel.com/developer/docs#mcp",
+  "bugs": {
+    "url": "https://app.aaa-sentinel.com/contact"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "scripts": {
+    "build": "esbuild src/cli.ts --bundle --platform=node --format=esm --target=node20 --outfile=dist/cli.js",
+    "prepublishOnly": "npm run build",
+    "test": "vitest run"
+  },
+  "devDependencies": {
+    "@types/node": "^22.0.0",
+    "esbuild": "^0.24.0",
+    "typescript": "^5.7.0",
+    "vitest": "^3.2.0",
+    "zod": "^4.6.7"
+  }
+}