AI agents use mysql_create_index 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 an index modifies database schema and metadata reversibly—it can be dropped or altered later—making it a Write operation rather than Destructive. However, this is high-severity because index creation on production tables can lock tables, degrade performance, or cause downtime depending on execution strategy (ALGORITHM=INPLACE vs ALGORITHM=COPY).
From the tool's definition Tool name 'mysql_create_index' indicates index creation on a MySQL database. No description provided, but sibling tools include destructive operations (drop_event, alter_event) and write operations (create_event, create_function, create_role,…
Documented attack patterns abuse exactly the kind of access mysql_create_index 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 mysql_create_index:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_create_index": {
"limits": [
{
"counter": "mysql_create_index_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mysql_create_index 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.
mysql_create_index. 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 mysql_create_index: 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.
mysql_create_index 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 mysql_create_index 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 mysql_create_index. 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.
mysql_create_index 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.