Create a user with SSL requirements.
AI agents use create_user_with_ssl to create or update resources in Mysql — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mysql environment.
Creating a new database user is a reversible Write operation—the user account can be modified or deleted later. However, it rates high severity because an AI agent creating arbitrary users on a production MySQL server could grant unintended access, compromise security posture, or enable privilege escalation.
From the tool's definition Tool name 'create_user_with_ssl' and description 'Create a user with SSL requirements' indicate user account creation, which is a Write operation (creates new data/entities in the database system).
Documented attack patterns abuse exactly the kind of access create_user_with_ssl gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for create_user_with_ssl:
{
"version": "1",
"default": "deny",
"tools": {
"create_user_with_ssl": {
"limits": [
{
"counter": "create_user_with_ssl_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_user_with_ssl 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 user with SSL requirements. It is categorised as a Write tool in the Mysql MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mysql MCP server in PolicyLayer and add a rule for create_user_with_ssl: 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 Mysql. Nothing to install.
create_user_with_ssl 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_user_with_ssl 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_user_with_ssl. 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_user_with_ssl is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mysql, 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.
233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.