Remove inbound access rules from AWS security groups to restrict network traffic and enhance infrastructure security.
MIT
299,485 tools. Last updated 2026-07-14 22:18
"Ingress" matching MCP tools:
- Add inbound traffic rules to AWS security groups to control network access for EC2 instances and other resources.MIT
- Modify descriptions for inbound security group rules in AWS to improve documentation and clarity of network access controls.MIT
- Summarize Kubernetes network policies with pod selectors, ingress/egress rule counts, and flag potential default-deny ingress configurations.MIT
- Create Kubernetes Ingress resources to route external traffic to backend services in specified namespaces.Apache 2.0
- Delete Kubernetes Ingress resources from specified namespaces to manage network access and routing rules in clusters.Apache 2.0
Matching MCP Servers
- FlicenseAqualityCmaintenanceEnables conversion of Nginx Ingress resources to AWS Gateway API (ALB/NLB) YAML through a conversational interface, with validation and migration reporting.Last updated5
Blekline MCP Serverofficial
Alicense-qualityAmaintenanceProvides AI ingress governance by masking prompts, classifying risk, and enforcing tool policies before agent calls reach model providers or sandboxes.Last updatedAGPL 3.0
- Update Kubernetes Ingress configurations to modify host routing and backend service connections for managing external access to applications.Apache 2.0
- Retrieve detailed information about a specific Kubernetes Ingress resource, including configuration and routing rules, to monitor and manage external access to services in your cluster.Apache 2.0
- Generate aggregated counts and time-series summaries for occupancy, people, line crossings, and custom events. Use for analytics and trends over intervals from minutes to years.MIT
- Analyze space utilization, traffic flow, peak hours, and scene activity across cameras to answer business questions.MIT
- Create a Docker network with specified name, driver, IPAM, and options. Supports bridge, overlay, swarm, and internal networks.MIT
- List active SIP dialogs currently using topology hiding. View the mapped keys rewriting Via, Contact, and Record-Route headers between ingress and egress legs for each dialog.Apache 2.0
- Identify currently failing Kubernetes resources: broken deployments, missing references, scheduling blockers, and false conditions. Get a ranked list with severity and diagnostic context.Apache 2.0
- Diagnose why a Kubernetes Ingress has no corresponding AVI Virtual Service by validating IngressClass, TLS secrets, and backend Services, returning issues and kubectl fix commands.MIT
- Retrieves security groups and their firewall rules, detailing ingress and egress settings with protocols, ports, and remote IP prefixes.MIT
- Analyze Kubernetes cluster configuration for security, reliability, and efficiency violations. Get remediation guidance for misconfigurations like privileged containers, missing PodDisruptionBudgets, and resource limits.Apache 2.0
- Shows mapping between Kubernetes Ingress resources and AVI Virtual Services to verify their correspondence.MIT
- List or fetch Kubernetes resources with summarized key fields. Read-only, idempotent, and never returns Secret/ConfigMap values.MIT
- Traces an AWS instance's full ingress path: from instance through target groups, load balancers, listeners, WebACL, and IP sets, and detects if it trusts forwarded client IPs.MIT
- Generate infrastructure diagrams as code for AWS, Azure, GCP, Kubernetes and other providers by defining nodes, connections and clusters programmatically.MIT