New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_instance_config

Delete a configuration profile for a Linode instance

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/delete-instance-config.md

What delete_instance_config does on Linode MCP Server

AI agents call delete_instance_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.

Why delete_instance_config is rated Critical

This tool permanently removes a configuration profile, which cannot be undone. Deleting instance configuration is destructive as it alters the instance's operational state irreversibly. While not as severe as deleting the instance itself, removing configuration profiles is a destructive operation with high blast radius if executed unintentionally against the wrong instance or profile.

From the tool's definition Tool name is 'delete_instance_config' with description 'Delete a configuration profile for a Linode instance'. The verb 'Delete' explicitly indicates irreversible removal of data.

Questions about delete_instance_config

What does the delete_instance_config tool do? +

Delete a configuration profile for a Linode instance. 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 delete_instance_config? +

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

delete_instance_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 delete_instance_config? +

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

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Linode MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.