list_records

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-records.md

WHAT IT DOES

What list_records does on Vultr MCP

AI agents call list_records 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_records is rated Low

List operations are purely informational queries that retrieve and display existing data without altering, deleting, or executing anything. No side effects are expected. The empty description reduces confidence slightly, but the naming pattern is unambiguous for a read operation.

From the tool's definition Tool name 'list_records' indicates a retrieval operation without modification. The name follows standard read-operation naming convention (list_*).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_records Allowed

list_records 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_records": {}
  }
}

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

FAQ

Questions about list_records

What does the list_records tool do? +

list_records 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_records? +

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

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

Can I rate-limit list_records? +

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

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

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