update_physical_network · CloudStack MCP Server MCP

WHAT IT DOES

What update_physical_network does on CloudStack MCP Server

AI agents use update_physical_network to create or update resources in CloudStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

WHY IT NEEDS A POLICY

Why update_physical_network needs a policy

This tool modifies network infrastructure configuration, which could impact service availability and network traffic routing across the entire cloud deployment. While reversible (hence Write rather than Destructive), misconfiguration could cause widespread connectivity issues. The high severity reflects the critical nature of physical network infrastructure in a cloud platform.

From the tool's definition Tool name and description indicate this updates (modifies) a physical network configuration. The verb 'update' represents a reversible modification operation. CloudStack physical networks are foundational infrastructure components.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_physical_network Rate-limited

update_physical_network stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_physical_network": {
      "limits": [
        {
          "counter": "update_physical_network_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about update_physical_network

What does the update_physical_network tool do? +

Update a physical network. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_physical_network? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for update_physical_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 CloudStack MCP Server. Nothing to install.

What risk level is update_physical_network? +

update_physical_network is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_physical_network? +

Yes. Add a rate_limit block to the update_physical_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.

How do I block update_physical_network completely? +

Set action: deny in the PolicyLayer policy for update_physical_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.

What MCP server provides update_physical_network? +

update_physical_network is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.