remove_nodebalancer_config

remove a port configuration from a NodeBalancer

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/remove-nodebalancer-config.md

WHAT IT DOES

What remove_nodebalancer_config does on Linode MCP Server

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

RISK

Why remove_nodebalancer_config is rated Critical

Removing a port configuration from a NodeBalancer is an irreversible deletion action that directly impacts production network traffic routing. Once removed, the configuration cannot be automatically recovered and would require manual reconfiguration.

From the tool's definition Tool name 'remove_nodebalancer_config' and description 'remove a port configuration from a NodeBalancer' indicate deletion of network load balancer configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_nodebalancer_config 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 remove_nodebalancer_config, this is the rule to start with:

remove_nodebalancer_config Hidden

remove_nodebalancer_config is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_nodebalancer_config"
  ]
}

RESTRICT 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 remove_nodebalancer_config call is checked against it from then on.

FAQ

Questions about remove_nodebalancer_config

What does the remove_nodebalancer_config tool do? +

remove a port configuration from a NodeBalancer. It is categorised as a Destructive tool in the Linode 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 remove_nodebalancer_config? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for remove_nodebalancer_config: 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 remove_nodebalancer_config? +

remove_nodebalancer_config 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 remove_nodebalancer_config? +

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

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

remove_nodebalancer_config 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 → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →