List Azure networking resources — VNets, NSGs, public IPs, load balancers.
AI agents call az_network to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Azure networking infrastructure metadata. It performs read-only operations to enumerate virtual networks, network security groups, public IP addresses, and load balancers. There are no side effects, no data modification, no code execution, and no destructive operations. This is a standard inventory/discovery tool appropriate for monitoring and auditing purposes.
From the tool's definition Tool name and description indicate listing/querying: 'List Azure networking resources — VNets, NSGs, public IPs, load balancers.' The verb 'List' and the passive enumeration of resource types confirms retrieval of data with no modification or execution.
Attacks that exploit this kind of access
List Azure networking resources — VNets, NSGs, public IPs, load balancers. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for az_network: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches RedisNexus. Nothing to install.
az_network is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the az_network rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for az_network. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
az_network is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →