get_mysql_instance

What get_mysql_instance does on Linode MCP Server

AI agents call get_mysql_instance to retrieve information from Linode MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_mysql_instance is rated Low

This tool performs a read-only query to retrieve information about a MySQL database instance. It has no side effects, does not modify data, does not execute commands, and does not affect infrastructure state. The blast radius of misuse is minimal—an AI agent could only retrieve details it may not be authorized to see, but cannot affect the instance itself.

From the tool's definition Tool name 'get_mysql_instance' and description 'Get details for a specific MySQL database instance' indicate a retrieval operation that queries database instance metadata without modifying, deleting, or executing operations.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_mysql_instance": {}
  }
}

Questions about get_mysql_instance