AI agents use create_mysql_user to create or update resources in cPanel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your cPanel MCP Server environment.
This tool creates a new MySQL user, which is a reversible modification to the database system. It does not execute arbitrary code (Execute), irreversibly delete data (Destructive), or move money (Financial). It is Write rather than Read because it modifies system state by adding a new user account.
From the tool's definition Tool name 'create_mysql_user' and description 'Create a new MySQL database user' indicate creation of a new database user account, which is a write operation that modifies the database user registry.
Documented attack patterns abuse exactly the kind of access create_mysql_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and cPanel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_mysql_user:
{
"version": "1",
"default": "deny",
"tools": {
"create_mysql_user": {
"limits": [
{
"counter": "create_mysql_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_mysql_user 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.
Free to start. No card required.
Create a new MySQL database user. It is categorised as a Write tool in the cPanel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for create_mysql_user: 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 cPanel MCP Server. Nothing to install.
create_mysql_user 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 create_mysql_user 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 create_mysql_user. 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.
create_mysql_user is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from cPanel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
164 cPanel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.