VPS_stopRecoveryModeV1

Stop recovery mode for a specified virtual machine. If virtual machine is not in recovery mode, this operation will fail. Use this endpoint to exit system rescue mode and return VPS to normal operation.

SERVERHostinger Api SOURCEhostinger-api-mcp
High RISK CLASS
Category Execute
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-stoprecoverymodev1.md

What VPS_stopRecoveryModeV1 does on Hostinger Api

AI agents invoke VPS_stopRecoveryModeV1 to trigger actions in Hostinger Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

ParameterTypeRequiredDescription
virtualMachineId integer Yes Virtual Machine ID

Parameters from the server's own tool schema.

Why VPS_stopRecoveryModeV1 is rated High

This tool triggers an external operation on a VPS infrastructure resource—exiting recovery/rescue mode and returning a system to normal operation. The effect depends on the VPS identifier provided as an argument.

From the tool's definition Stop recovery mode for a specified virtual machine. Use this endpoint to exit system rescue mode and return VPS to normal operation.

Questions about VPS_stopRecoveryModeV1

What does the VPS_stopRecoveryModeV1 tool do? +

Stop recovery mode for a specified virtual machine. If virtual machine is not in recovery mode, this operation will fail. Use this endpoint to exit system rescue mode and return VPS to normal operation. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does VPS_stopRecoveryModeV1 accept? +

VPS_stopRecoveryModeV1 accepts 1 parameter: virtualMachineId. Required: virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_stopRecoveryModeV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_stopRecoveryModeV1: 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 Hostinger Api. Nothing to install.

What risk level is VPS_stopRecoveryModeV1? +

VPS_stopRecoveryModeV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit VPS_stopRecoveryModeV1? +

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

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

VPS_stopRecoveryModeV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Hostinger Api, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.