Skip to main content
Glama

azure_analyze_nsg_rules

Analyzes Azure NSG rules to identify open management ports, overly permissive rules, and validates service endpoints and load balancer associations for security misconfigurations.

Instructions

ENHANCED v1.14.0 Automated Network Security Group (NSG) security analysis with service endpoints and load balancer integration validation. Identifies: open management ports (RDP 3389, SSH 22, WinRM 5985/5986), database ports (SQL 1433, MySQL 3306, PostgreSQL 5432, MongoDB 27017), wildcard source rules (0.0.0.0/0, Internet, Any), overly permissive rules, service endpoint security, load balancer backend pool NSG associations. Returns findings with risk severity and remediation recommendations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionIdYesAzure subscription ID
resourceGroupNoOptional: Filter by specific resource group
nsgNameNoOptional: Analyze specific NSG by name
validateServiceEndpointsNoValidate service endpoints security (checks if NSGs allow access to Azure Storage, SQL, etc.). Default: true
checkLoadBalancersNoCheck NSG associations with load balancer backend pools for security misconfigurations. Default: true
formatNoOutput format: 'markdown' (default, human-readable) or 'json' (machine-readable)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose behavioral traits like read-only nature, authentication requirements, or rate limits. It only implies a read operation by stating it returns findings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose with 'ENHANCED v1.14.0' clutter, but it is front-loaded with purpose and structured as a list of checks, making it adequate though not optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description vaguely states 'returns findings with risk severity and remediation recommendations' but lacks specifics on output structure, leaving moderate gaps for an automated analysis tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds value by detailing specific checks (e.g., ports, service endpoints, load balancers) that map to parameters, enriching the schema information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it performs automated NSG security analysis with specific checks including ports and rules, distinguishing it from sibling tools that analyze other Azure resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for NSG security analysis but does not explicitly state when to use this tool vs. alternatives or provide exclusions, leaving usage context implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/h4cd0c/stratos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server