Rebuild all indexes for a table.
AI agents invoke rebuild_table_indexes to trigger actions in Mysql. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Rebuilding all indexes for a table is a non-trivial database operation that rewrites index data structures, potentially locking the table and consuming significant I/O and CPU resources. While it is reversible in the sense that no data is permanently deleted, it is not a simple read or write — it executes a structural maintenance operation (akin to ALTER TABLE ...
From the tool's definition 'Rebuild all indexes for a table' — rebuilding indexes is a heavyweight DDL-adjacent operation that rewrites index structures on disk
Documented attack patterns abuse exactly the kind of access rebuild_table_indexes 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 rebuild_table_indexes:
{
"version": "1",
"default": "deny",
"tools": {
"rebuild_table_indexes": {
"limits": [
{
"counter": "rebuild_table_indexes_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}rebuild_table_indexes stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Rebuild all indexes for a table. It is categorised as a Execute tool in the Mysql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mysql MCP server in PolicyLayer and add a rule for rebuild_table_indexes: 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.
rebuild_table_indexes is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rebuild_table_indexes 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 rebuild_table_indexes. 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.
rebuild_table_indexes 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.