disable_static_nat · CloudStack MCP Server MCP

WHAT IT DOES

What disable_static_nat does on CloudStack MCP Server

AI agents use disable_static_nat 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 disable_static_nat needs a policy

This tool modifies network address translation rules, which is a reversible configuration change (Write category). It affects network connectivity and routing but can be re-enabled or reconfigured.

From the tool's definition Tool name 'disable_static_nat' and description 'Disable static NAT for IP address' indicate modification of network configuration. This reverses a static NAT rule without deleting underlying resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_static_nat Rate-limited

disable_static_nat 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": {
    "disable_static_nat": {
      "limits": [
        {
          "counter": "disable_static_nat_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 disable_static_nat

What does the disable_static_nat tool do? +

Disable static NAT for IP address. 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 disable_static_nat? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for disable_static_nat: 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 disable_static_nat? +

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

Can I rate-limit disable_static_nat? +

Yes. Add a rate_limit block to the disable_static_nat 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 disable_static_nat completely? +

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

disable_static_nat 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.