This record as markdown: /tools/rsp2k-mcp-vultr/list-by-status.md
What list_by_status does on Vultr MCP
AI agents call list_by_status 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_by_status is rated Low
This tool performs a retrieval operation on storage gateway resources, filtering by status. It only reads and lists data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could retrieve information it shouldn't have access to, but cannot cause infrastructure damage or data loss. Classified as Read with low severity.
From the tool's definition Tool name 'list_by_status' and description 'List storage gateways by status' indicate a query operation that retrieves and filters existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_by_status 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_by_status, this is the rule to start with:
list_by_status 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_by_status call is checked against it from then on.
Questions about list_by_status
List storage gateways by status. 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_by_status: 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_by_status 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_by_status 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_by_status. 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_by_status 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