Order a VPS. product = plan slug from list_plans; os_id = an OS id from that plan's images. Optional hostname and ssh_key (public key — strongly recommended so you get key-based root login). Branching on the response: • paid_from_balance: true → the prepaid balance covered it; the server is provi...
Risk signalsAccepts URL/endpoint input (hostname) · Admin/system-level operation
Part of the EQVPS — Crypto VPS for AI agents server.
Free to start. No card required.
AI agents call order_vps to retrieve information from EQVPS — Crypto VPS for AI agents without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though order_vps only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"order_vps": {}
}
} See the full EQVPS — Crypto VPS for AI agents policy for all 16 tools.
These attack patterns abuse exactly the kind of access order_vps gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Order a VPS. product = plan slug from list_plans; os_id = an OS id from that plan's images. Optional hostname and ssh_key (public key — strongly recommended so you get key-based root login). Branching on the response: • paid_from_balance: true → the prepaid balance covered it; the server is provisioning. Poll get_vps_status until status is active and the VM is reachable. • paid_from_balance: false → balance was insufficient; an unpaid invoice is returned. Call pay_invoice with invoice.id to get a crypto checkout_url, OR topup_balance then re-order.. It is categorised as a Read tool in the EQVPS — Crypto VPS for AI agents MCP Server, which means it retrieves data without modifying state.
Register the EQVPS — Crypto VPS for AI agents MCP server in PolicyLayer and add a rule for order_vps: 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 EQVPS — Crypto VPS for AI agents. Nothing to install.
order_vps 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 order_vps 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 order_vps. 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.
order_vps is provided by the EQVPS — Crypto VPS for AI agents MCP server (https://mcp.eqvps.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 EQVPS — Crypto VPS for AI agents tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.