unassign_instances

Unassign Linode instances from a placement group

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/unassign-instances.md

WHAT IT DOES

What unassign_instances does on Linode MCP Server

AI agents use unassign_instances to create or update resources in Linode MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.

RISK

Why unassign_instances is rated Medium

Unassigning instances from a placement group modifies the placement configuration reversibly — instances can be reassigned. This is a Write operation as it changes resource associations without destroying the instances themselves. Misuse could cause unintended placement policy violations affecting performance or availability.

From the tool's definition Unassign Linode instances from a placement group

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs unassign_instances safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unassign_instances, this is the rule to start with:

unassign_instances Rate-limited

unassign_instances stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unassign_instances": {
      "limits": [
        {
          "counter": "unassign_instances_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every unassign_instances call is checked against it from then on.

FAQ

Questions about unassign_instances

What does the unassign_instances tool do? +

Unassign Linode instances from a placement group. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on unassign_instances? +

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

What risk level is unassign_instances? +

unassign_instances is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit unassign_instances? +

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

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

unassign_instances is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Linode MCP Server, and thousands of servers like it.

This server

All 416 Linode MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →