AUTO-OPTIMIZE: Scans a Fabric Eventhouse for all fixable issues across all KQL databases and applies fixes.
AI agents invoke eventhouse_auto_optimize 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 automatically applies fixes across all KQL databases in an Eventhouse. It both analyzes and modifies configurations/settings at scale. While it may be partially reversible, the automated mass-application of fixes across all databases without per-change review makes it Execute-level risk.
From the tool's definition 'Scans a Fabric Eventhouse for all fixable issues across all KQL databases and applies fixes'
Documented attack patterns abuse exactly the kind of access eventhouse_auto_optimize 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 eventhouse_auto_optimize:
{
"version": "1",
"default": "deny",
"tools": {
"eventhouse_auto_optimize": {
"limits": [
{
"counter": "eventhouse_auto_optimize_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} eventhouse_auto_optimize 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.
AUTO-OPTIMIZE: Scans a Fabric Eventhouse for all fixable issues across all KQL databases and applies fixes. 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 eventhouse_auto_optimize: 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.
eventhouse_auto_optimize 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 eventhouse_auto_optimize 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 eventhouse_auto_optimize. 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.
eventhouse_auto_optimize 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.