AI agents invoke rebuild_table_indexes to trigger actions in Mcp Windows. 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 indexes alters the physical storage and internal structure of a database table. While not purely destructive (data is not deleted), it is an irreversible structural operation that rewrites index data, can lock tables, consume significant I/O and CPU, and may cause downtime or performance degradation if misused.
From the tool's definition 'Rebuild all indexes for a table' — rebuilding indexes is a resource-intensive operation that modifies database internal structures
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 Mcp Windows, 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 Mcp Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Windows 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 Mcp Windows. 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 Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.