This record as markdown: /tools/rsp2k-mcp-vultr/list-groups.md
What list_groups does on Vultr MCP
AI agents call list_groups 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_groups is rated Low
The tool appears to retrieve or enumerate groups within the Vultr infrastructure, consistent with a Read operation. No modification, execution, deletion, or financial action is suggested by the name. The low severity reflects the minimal risk of a simple listing operation—it exposes information but cannot modify or damage resources.
From the tool's definition Tool name 'list_groups' indicates a listing/retrieval operation with no apparent side effects. The naming convention matches the Read category pattern (list*, get*, fetch*).
Attacks that exploit this kind of access
The rule that runs list_groups 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_groups, this is the rule to start with:
list_groups 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_groups call is checked against it from then on.
Questions about list_groups
list_groups 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.
Register the Vultr MCP server in PolicyLayer and add a rule for list_groups: 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_groups 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_groups 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_groups. 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_groups 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