Critical Risk →

delete_startup_script

Delete a startup script.

How to control delete_startup_script ↓

What delete_startup_script does on Vultr MCP

AI agents call delete_startup_script to permanently remove resources in Vultr MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_startup_script needs a policy

This tool performs an irreversible deletion operation on a startup script resource. Once deleted, the script cannot be recovered without external backups. While the blast radius is somewhat contained (limited to a single script resource rather than bulk deletion), the destructive nature and the potential impact if a critical startup script is removed justifies 'high' severity.

From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a startup script.' The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_startup_script gives an agent:

How to control delete_startup_script

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 delete_startup_script:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_startup_script"
  ]
}

delete_startup_script disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Vultr MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_startup_script

What does the delete_startup_script tool do? +

Delete a startup script. It is categorised as a Destructive tool in the Vultr MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_startup_script? +

Register the Vultr MCP server in PolicyLayer and add a rule for delete_startup_script: 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.

What risk level is delete_startup_script? +

delete_startup_script is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_startup_script? +

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

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

delete_startup_script 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.

Enforce policy on every Vultr MCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.