enable_static_nat
Enable static NAT for IP address
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/enable-static-nat.md
What enable_static_nat does on CloudStack MCP Server
AI agents use enable_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 enable_static_nat is rated Medium
This tool modifies network infrastructure by enabling a static NAT rule for an IP address. While the change is reversible (can be disabled), it alters network routing and traffic flow, making it a Write operation rather than Read. It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).
From the tool's definition Tool name 'enable_static_nat' and description 'Enable static NAT for IP address' indicate modification of network configuration.
Attacks that exploit this kind of access
The rule that runs enable_static_nat 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 enable_static_nat, this is the rule to start with:
enable_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.
The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every enable_static_nat call is checked against it from then on.
Questions about enable_static_nat
Enable 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.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for enable_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.
enable_static_nat is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enable_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.
Set action: deny in the PolicyLayer policy for enable_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.
enable_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.
More on CloudStack MCP Server, and thousands of servers like it.
This server
Across the catalogue