suspend_mysql_instance

Suspend a MySQL database 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/suspend-mysql-instance.md

WHAT IT DOES

What suspend_mysql_instance does on Linode MCP Server

AI agents call suspend_mysql_instance 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 suspend_mysql_instance is rated Critical

Suspending a database instance makes it unavailable to applications, which is effectively an irreversible operational state change (until explicitly resumed) that can cause data access loss, service outages, and disruption to dependent applications. While not a permanent deletion, suspension of a production database has a high blast radius and the action is not trivially undone without additional steps.

From the tool's definition Suspend a MySQL database instance

Attacks that exploit this kind of access

RECOMMENDED RULE

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

suspend_mysql_instance Hidden

suspend_mysql_instance 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": [
    "suspend_mysql_instance"
  ]
}

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

FAQ

Questions about suspend_mysql_instance

What does the suspend_mysql_instance tool do? +

Suspend a MySQL database 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 suspend_mysql_instance? +

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

What risk level is suspend_mysql_instance? +

suspend_mysql_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 suspend_mysql_instance? +

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

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

suspend_mysql_instance 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

delete_mysql_database on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →