This record as markdown: /tools/rsp2k-mcp-vultr/get-iso.md
What get_iso does on Vultr MCP
AI agents call get_iso 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 get_iso is rated Low
This tool retrieves information about an ISO image without modifying any resources, executing code, or triggering external operations. It is a simple read operation that queries metadata about a specific ISO, which is consistent with the 'Read' category for operations that retrieve or query data with no side effects.
From the tool's definition Tool name is 'get_iso' and description states 'Get details of a specific ISO image' - this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_iso 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 get_iso, this is the rule to start with:
get_iso 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 get_iso call is checked against it from then on.
Questions about get_iso
Get details of a specific ISO image. 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 get_iso: 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.
get_iso 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 get_iso 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 get_iso. 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.
get_iso 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