This record as markdown: /tools/aapanel-mcp/config-set-username.md
What config_set_username does on Aapanel
AI agents use config_set_username to create or update resources in Aapanel, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aapanel environment.
Why config_set_username is rated Medium
This tool modifies a critical authentication credential (admin username) reversibly, making it Write category. Severity is high because compromising or changing admin credentials grants unauthorized control over the entire aaPanel system and all hosted services. An AI agent with this capability could lock out legitimate administrators or create backdoor access.
From the tool's definition Tool description states 'Change the panel admin username' — this modifies an existing administrative credential.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs config_set_username safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For config_set_username, this is the rule to start with:
config_set_username stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every config_set_username call is checked against it from then on.
Questions about config_set_username
Change the panel admin username. It is categorised as a Write tool in the Aapanel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aapanel MCP server in PolicyLayer and add a rule for config_set_username: 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 Aapanel. Nothing to install.
config_set_username is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the config_set_username 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.
Set action: deny in the PolicyLayer policy for config_set_username. 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.
config_set_username is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue