list_physical_networks

What list_physical_networks does on CloudStack MCP Server

AI agents call list_physical_networks to retrieve information from CloudStack MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_physical_networks is rated Low

This is a straightforward list/query operation that retrieves existing infrastructure information. It has no side effects, does not modify state, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an agent could only view network configuration information that likely requires access to be read anyway in normal CloudStack operations.

From the tool's definition Tool name 'list_physical_networks' and description 'List physical networks' indicate a query operation that retrieves information about physical networks without modifying, deleting, or executing operations.

The rule that runs list_physical_networks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_physical_networks, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_physical_networks": {}
  }
}

Questions about list_physical_networks