AI agents invoke start to trigger actions in Vultr MCP. 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.
Starting a stopped instance is an Execute-category action because it triggers external infrastructure operations with side effects. While not Destructive (reversible via stop), it goes beyond Read/Write data operations—it executes commands that change system state. Severity is high due to potential blast radius: starting unintended instances could incur costs, affect production services, or expose security surfaces.
From the tool's definition Tool name 'start' with description 'Start a stopped instance' indicates execution of a state-change operation on cloud infrastructure. The action triggers external effects (VM startup) whose consequences depend on the instance targeted.
Documented attack patterns abuse exactly the kind of access start gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vultr MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for start:
{
"version": "1",
"default": "deny",
"tools": {
"start": {
"limits": [
{
"counter": "start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start 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.
Free to start. No card required.
Start a stopped instance. It is categorised as a Execute tool in the Vultr MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vultr MCP server in PolicyLayer and add a rule for start: 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.
start 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 start 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 start. 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.
start 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.
Start from Vultr MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
284 Vultr MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.