list_private_gateways

A read tool on the CloudStack MCP server.

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/list-private-gateways.md

WHAT IT DOES

What list_private_gateways does on CloudStack MCP Server

AI agents call list_private_gateways 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.

RISK

Why list_private_gateways is rated Low

This tool queries and returns information about existing private gateways in CloudStack infrastructure. It performs a read-only operation with no side effects, no data modification, no execution of commands, and no destructive capabilities. The blast radius of misuse is minimal—an attacker gains only informational access to gateway configuration details.

From the tool's definition Tool name is 'list_private_gateways' and description states 'List private gateways' — a retrieval operation with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_private_gateways 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_private_gateways, this is the rule to start with:

list_private_gateways Allowed

list_private_gateways is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every list_private_gateways call is checked against it from then on.

FAQ

Questions about list_private_gateways

What does the list_private_gateways tool do? +

list_private_gateways is a read tool on the CloudStack MCP Server MCP server. It is categorised as a Read tool in the CloudStack MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_private_gateways? +

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

list_private_gateways is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_private_gateways? +

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

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

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

KEEP EXPLORING

More on CloudStack MCP Server, and thousands of servers like it.

This server

All 442 CloudStack MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →