aapanel-mcp

Get or reset the MySQL root password

danger_mysql_root_password

Destructive

Read or set the MySQL root password on an aaPanel server, but only when AAPANEL_ALLOW_DANGEROUS is enabled; otherwise access is denied.

Instructions

Read the MySQL root password, or set a new one when password is supplied. This is the highest-privilege credential on the box: the server refuses to expose it unless AAPANEL_ALLOW_DANGEROUS is set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "danger_mysql_root_password"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No	Config row id.
`key`	No	Key to read, normally mysql_root.	mysql_root
`table`	No	Table to read, normally config.	config

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1-alpha.0Sep 29, 2026

TDQS

A3.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotency. The description adds genuinely useful context beyond them: this is the highest-privilege credential on the box and the server refuses to expose it unless an environment flag is set, which is an auth precondition the agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste: the dual behavior leads and the security precondition follows. Front-loaded and appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is needed for a credential read, and the auth gate is disclosed. But the description leaves the write path under-specified (no password parameter, no indication of what is overwritten or whether the change is reversible), which is a meaningful gap for a destructive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for id/key/table, so the baseline would be 3. However, the description's only parameter reference is 'when password is supplied', and no password parameter exists in the schema. That mismatch creates real ambiguity about how the write mode is actually triggered and undermines the otherwise self-documenting schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific dual purpose (read the MySQL root password, or set a new one) with the resource named precisely. It does not, however, differentiate itself from the sibling danger_mysql_reset_root_password, which appears to overlap with the 'set a new one' behavior, leaving the agent to guess which to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives the condition that switches modes ('when password is supplied') and names a hard prerequisite (AAPANEL_ALLOW_DANGEROUS must be set). But it never says when to prefer this over danger_mysql_reset_root_password, so the agent has no explicit routing guidance between two apparently overlapping tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server