This record as markdown: /tools/hostinger-mcp/vps-docker-restart.md
What vps_docker_restart does on Hostinger
AI agents invoke vps_docker_restart to trigger actions in Hostinger. 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.
Why vps_docker_restart is rated High
Restarting a Docker project is an Execute action—it triggers an external operation (container/service restart) whose effects depend on the argument (which project). While not destructive (data persists), it causes service disruption and depends entirely on what is running in that Docker environment. Misuse could interrupt production services, making it high severity.
From the tool's definition Tool name 'vps_docker_restart' and description 'Restart a Docker project' indicate execution of a restart operation on a running service.
Attacks that exploit this kind of access
The rule that runs vps_docker_restart safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vps_docker_restart, this is the rule to start with:
vps_docker_restart stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every vps_docker_restart call is checked against it from then on.
Questions about vps_docker_restart
Restart a Docker project. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hostinger MCP server in PolicyLayer and add a rule for vps_docker_restart: 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. Nothing to install.
vps_docker_restart is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vps_docker_restart 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 vps_docker_restart. 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.
vps_docker_restart is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
Across the catalogue