list_instance_networks

A read tool on the Vultr MCP server.

SERVERVultr MCP SOURCErsp2k/mcp-vultr

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/rsp2k-mcp-vultr/list-instance-networks.md

WHAT IT DOES

What list_instance_networks does on Vultr MCP

AI agents call list_instance_networks to retrieve information from Vultr MCP 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_instance_networks is rated Low

This tool retrieves network information associated with instances. The 'list' prefix universally indicates a query operation that retrieves existing data without modification, deletion, or execution of arbitrary code. The empty description reduces confidence slightly, but the naming convention is unambiguous. This poses minimal risk as it merely reads infrastructure state.

From the tool's definition Tool name 'list_instance_networks' indicates a listing/retrieval operation. Description is empty, but the verb 'list' is a clear indicator of read-only data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_instance_networks safely

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

list_instance_networks Allowed

list_instance_networks 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_instance_networks": {}
  }
}

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

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

FAQ

Questions about list_instance_networks

What does the list_instance_networks tool do? +

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

How do I enforce a policy on list_instance_networks? +

Register the Vultr MCP server in PolicyLayer and add a rule for list_instance_networks: 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 Vultr MCP. Nothing to install.

What risk level is list_instance_networks? +

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

Can I rate-limit list_instance_networks? +

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

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

list_instance_networks is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vultr, and thousands of servers like it.

This server

All 284 Vultr 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 →