vnet
Virtual Network information
How to use it
Project documentation lists vnet for the Aks MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Aks MCP
<path of binary aks-mcp>Other tools in Aks MCP (39)
(admin access level):
AKS cluster resource ID
Get information about all network resources
Execute KQL queries against Application Insights telemetry data
(required for runbycategory operation): Detector category
The complete Azure CLI command to execute (e.g., az aks list --resource-group myRG, az vm list --subscription <sub-id>)
Query AKS control plane logs with safety constraints
Deploy Inspektor Gadget to the cluster (via the AKS cluster extension)
(required for run operation): Name of the detector to run
Check if AKS cluster has diagnostic settings configured
(required for run and runbycategory operations): End time in UTC ISO format (within last 30 days, max 24h from start)
Filter logs by keyword (case-insensitive text match)
Get runtime status
VMSS instance ID
Metadata management (label, annotate, set)
Workload lifecycle (run, expose, scale, autoscale, rollout)
Log level filter (ERROR, WARN, INFO)
Number of recent log lines to return (default: 500, max: 2000)
Load Balancer information
Type of logs to collect (kubelet, containerd, kernel, syslog)
List metric values for resources
Network Security Group information
(required): Operation to perform (list, run, or runbycategory)
Private endpoint information
(all access levels):
(readwrite/admin access levels):
Only read operations are allowed
Reimage VMSS instances (VM not supported for reimage)
Generate recommendation reports
Retrieve resource health events for AKS clusters
Restart VM/VMSS instances
Route Table information
Run a specific AKS diagnostic detector
Run all detectors in a specific category
Time range for logs (e.g., 1h, 30m, 2d) - takes precedence over lines
(required for run and runbycategory operations): Start time in UTC ISO format (within last 30 days)
Subnet information
Optional timeout in seconds (default: 120)
VMSS name (obtain from getaksvmssinfo or kubectl get nodes)