list_pxe_scripts

List PXE startup scripts.

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-pxe-scripts.md

WHAT IT DOES

What list_pxe_scripts does on Vultr MCP

AI agents call list_pxe_scripts 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_pxe_scripts is rated Low

This tool retrieves and displays existing PXE (Preboot eXecution Environment) startup scripts without creating, modifying, or deleting any resources. It is a read-only operation that poses minimal security risk even if misused by an AI agent, as it only exposes information about existing scripts rather than altering infrastructure.

From the tool's definition Tool name 'list_pxe_scripts' and description 'List PXE startup scripts' indicate a query/retrieval operation with no modification or destructive capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_pxe_scripts Allowed

list_pxe_scripts 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_pxe_scripts": {}
  }
}

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_pxe_scripts call is checked against it from then on.

FAQ

Questions about list_pxe_scripts

What does the list_pxe_scripts tool do? +

List PXE startup scripts. 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_pxe_scripts? +

Register the Vultr MCP server in PolicyLayer and add a rule for list_pxe_scripts: 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_pxe_scripts? +

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

Can I rate-limit list_pxe_scripts? +

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

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

list_pxe_scripts 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 →