Gate 1
Traffic coverage
Map hosts, resources, web ACLs, API and MCP paths, methods, streaming, clients, authentication schemes, alternate routes, and every path that bypasses AWS WAF.
Third-party managed rule evaluation
AWS WAF MCP Threat Detection Readiness
Describe the protected resources, API and MCP routes, authentication, clients, traffic, Marketplace contract, logging, test corpus, downstream permissions, exception process, and budget. Generate a staged plan without treating one rule group as complete MCP security.
Four readiness gates
Gate 2
Rule contract
Record the Salt Marketplace subscription, current Regions, price, capacity, version, rules, default actions, labels, overrides, support, and change policy.
Gate 3
Detection evidence
Replay legitimate traffic plus missing and expired credentials, enumeration, GraphQL abuse, SSRF-like inputs, JWT anomalies, prototype pollution, retries, and large or streaming requests.
Gate 4
Authorization and operations
Verify identity, tenant and tool authorization, argument validation, sensitive-action approval, logs, redaction, alerts, exceptions, owners, incident response, cost, and rollback.
Choose the next safe state
Stage in observe mode
Coverage and telemetry are known, but legitimate-client baselines, false positives, rule actions, or exception ownership still need evidence.
Enforce narrowly
A named endpoint and traffic cohort pass adversarial tests, logging review, authorization checks, cost review, and rollback rehearsal.
Hold deployment
Traffic bypasses the web ACL, identity is ambiguous, logs expose sensitive data, blocking breaks critical clients, or no rollback owner exists.
Minimum evidence packet
Preserve the subscription and version, web ACL scope, rule actions, replay corpus, false blocks, missed detections, log and redaction review, authorization tests, exceptions with expiry, dashboards, full cost, approvers, and rollback result.
Read the deployment guide
AWS WAF Salt rules for MCP threat detectionReview launch coverage, the web ACL boundary, rollout sequence, layered authorization, version control, cost, and rollback.Official facts checked August 15, 2026. Recheck the AWS announcement, Marketplace listing, Regions, price, rule reference, versions, and AWS WAF documentation.
Frequently Asked Questions
It turns the traffic, Marketplace, rule, test, authorization, logging, operations, and cost facts you provide into a staged evaluation plan. It does not access AWS, subscribe to the product, or change a web ACL.
No. AWS announced it as a Salt Security third-party managed rule group available through AWS Marketplace. Salt sets the Marketplace price and maintains the product contract.
No. It addresses listed request patterns on covered AWS WAF traffic. MCP identity, authorization, tool scope, arguments, prompt injection, downstream permissions, and uncovered paths require other controls.
First verify how every legitimate client authenticates, inspect the current rule action, test missing and malformed credentials, review logs and exceptions, then promote only the proven scope with rollback.