Critical Risk →

delete-gpu-instance

delete-gpu-instance

How to control delete-gpu-instance ↓

What delete-gpu-instance does on Novita MCP Server

AI agents call delete-gpu-instance to permanently remove resources in Novita MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete-gpu-instance needs a policy

This tool performs an irreversible deletion operation on GPU instances. Deleting a GPU instance cannot be undone and results in permanent loss of that computational resource. This fits the Destructive category as it removes data/resources permanently.

From the tool's definition Tool name is 'delete-gpu-instance' with no description provided. The 'delete' prefix indicates irreversible removal of a GPU instance resource.

Documented attack patterns abuse exactly the kind of access delete-gpu-instance gives an agent:

How to control delete-gpu-instance

PolicyLayer is an MCP gateway — it sits between your AI agents and Novita MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-gpu-instance:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-gpu-instance"
  ]
}

delete-gpu-instance 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 Novita MCP Server — 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-gpu-instance

What does the delete-gpu-instance tool do? +

delete-gpu-instance. It is categorised as a Destructive tool in the Novita MCP Server 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-gpu-instance? +

Register the Novita MCP Server MCP server in PolicyLayer and add a rule for delete-gpu-instance: 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 Novita MCP Server. Nothing to install.

What risk level is delete-gpu-instance? +

delete-gpu-instance 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-gpu-instance? +

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

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

delete-gpu-instance is provided by the Novita MCP Server MCP server (novitalabs/novita-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Novita MCP Server tool call.

Start from Novita MCP Server, 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.

20 Novita MCP Server 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.