Run table maintenance (OPTIMIZE with V-Order, Z-ORDER, VACUUM) on a Fabric Lakehouse.
AI agents invoke lakehouse_run_table_maintenance to trigger actions in Force Fabric MCP Server. 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.
This tool executes database maintenance operations (OPTIMIZE, Z-ORDER, VACUUM) that alter the physical state of tables. While not strictly destructive (data is not deleted), these are Execute operations because they trigger external database operations whose effects are determined by the table structure and data passed to them.
From the tool's definition Tool description states it "Run[s] table maintenance (OPTIMIZE with V-Order, Z-ORDER, VACUUM)" on a Lakehouse, which are irreversible data structure operations that modify underlying table organization and storage.
Documented attack patterns abuse exactly the kind of access lakehouse_run_table_maintenance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Force Fabric MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for lakehouse_run_table_maintenance:
{
"version": "1",
"default": "deny",
"tools": {
"lakehouse_run_table_maintenance": {
"limits": [
{
"counter": "lakehouse_run_table_maintenance_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}lakehouse_run_table_maintenance 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.
Run table maintenance (OPTIMIZE with V-Order, Z-ORDER, VACUUM) on a Fabric Lakehouse. It is categorised as a Execute tool in the Force Fabric MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Force Fabric MCP Server MCP server in PolicyLayer and add a rule for lakehouse_run_table_maintenance: 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 Force Fabric MCP Server. Nothing to install.
lakehouse_run_table_maintenance 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 lakehouse_run_table_maintenance 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 lakehouse_run_table_maintenance. 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.
lakehouse_run_table_maintenance is provided by the Force Fabric MCP Server MCP server (tmdaidevs/force-fabric-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Force Fabric 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.
33 Force Fabric MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.