This record as markdown: /tools/rsp2k-mcp-vultr/list-bare-metal-servers.md
What list_bare_metal_servers does on Vultr MCP
AI agents call list_bare_metal_servers 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.
Why list_bare_metal_servers is rated Low
This tool queries and returns information about existing bare metal server resources without creating, modifying, deleting, or executing any operations. It is a read-only operation with minimal blast radius if misused—at worst, an attacker gains visibility into existing infrastructure inventory.
From the tool's definition Tool name 'list_bare_metal_servers' and description 'List all bare metal servers' indicate a data retrieval operation with no modification or execution of infrastructure.
Attacks that exploit this kind of access
The rule that runs list_bare_metal_servers 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_bare_metal_servers, this is the rule to start with:
list_bare_metal_servers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every list_bare_metal_servers call is checked against it from then on.
Questions about list_bare_metal_servers
List all bare metal servers. It is categorised as a Read tool in the Vultr MCP MCP Server, which means it retrieves data without modifying state.
Register the Vultr MCP server in PolicyLayer and add a rule for list_bare_metal_servers: 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.
list_bare_metal_servers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_bare_metal_servers 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 list_bare_metal_servers. 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.
list_bare_metal_servers 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.
More on Vultr, and thousands of servers like it.
This server
Across the catalogue