Force Fabric MCP Server

33 tools. 16 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

16 can modify or destroy data
17 read-only
33 tools total

Community server · catalogue entry verified 11/06/2026

How to control Force Fabric MCP Server ↓

What Force Fabric MCP Server exposes to your agents

Read (17) Write / Execute (14) Destructive / Financial (1)
Critical Risk

The most dangerous Force Fabric MCP Server tools

16 of Force Fabric MCP Server's 33 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Force Fabric MCP Server

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. These are the rules we recommend:

Deny destructive operations
{
  "auth_logout": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "semantic_model_auto_optimize": {
    "limits": [
      {
        "counter": "semantic_model_auto_optimize_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "auth_status": {
    "limits": [
      {
        "counter": "auth_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Force Fabric MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON FORCE FABRIC →

Free to start. No card required.

All 33 Force Fabric MCP Server tools

EXECUTE 13 tools
Execute lakehouse_run_table_maintenance Run table maintenance (OPTIMIZE with V-Order, Z-ORDER, VACUUM) on a Fabric Lakehouse. Execute eventhouse_auto_optimize AUTO-OPTIMIZE: Scans a Fabric Eventhouse for all fixable issues across all KQL databases and applies fixes. Execute eventhouse_fix AUTO-FIX: Applies fixes to a Fabric Eventhouse. Execute eventhouse_fix_materialized_views AUTO-FIX: Diagnoses and repairs broken materialized views in a Fabric Eventhouse. Execute gateway_fix AUTO-FIX: Applies fixes to gateway and connection issues. Execute lakehouse_auto_optimize AUTO-OPTIMIZE: Discovers ALL Delta tables in a Lakehouse and applies fixes to every table Execute lakehouse_fix AUTO-FIX: Applies Spark SQL fixes to a Lakehouse via Livy API (no notebooks needed). Execute semantic_model_fix AUTO-FIX: Uses XMLA/TMSL commands for atomic per-object fixes (measures, columns, tables). Execute semantic_model_optimization_recommendations LIVE SCAN: Connects to a Fabric Semantic Model and executes DAX queries (COLUMNSTATISTICS) Execute warehouse_analyze_query_patterns LIVE SCAN: Connects to a Fabric Warehouse SQL endpoint and analyzes real query execution Execute warehouse_auto_optimize AUTO-OPTIMIZE: Scans a Fabric Warehouse for all fixable issues and applies all safe fixes automatically. Execute warehouse_fix AUTO-FIX: Connects to a Fabric Warehouse and applies fixes for detected issues. Execute warehouse_optimization_recommendations LIVE SCAN: Connects to a Fabric Warehouse SQL endpoint and runs real diagnostic queries.
READ 17 tools
Read auth_status Check if you are currently authenticated to Microsoft Fabric. Read eventhouse_list List all eventhouses in a Fabric workspace with their query/ingestion URIs and KQL database counts. Read eventhouse_list_kql_databases List all KQL databases in a Fabric workspace. Read eventhouse_optimization_recommendations LIVE SCAN: Connects to a Fabric Eventhouse KQL endpoint and runs real diagnostic commands. Read fabric_optimization_report Generate a comprehensive optimization report for an entire Fabric workspace. Read gateway_list List all gateways with their status, version, type, and VNet configuration. Read gateway_list_connections List all connections with their connectivity type, gateway binding, and privacy level. Read gateway_optimization_recommendations LIVE SCAN: Scans all gateways and connections with 12 rules covering availability (online status, connectivity Read lakehouse_get_job_status Check the status of a table maintenance job on a Fabric Lakehouse. Read lakehouse_list List all lakehouses in a Fabric workspace with their metadata, SQL endpoint status, and OneLake paths. Read lakehouse_list_tables List all tables in a Fabric Lakehouse with their type, format (Delta/Parquet), and location. Read lakehouse_optimization_recommendations LIVE SCAN: Analyzes a Fabric Lakehouse by checking table formats (Delta vs non-Delta), Read semantic_model_list List all semantic models in a Fabric workspace. Read warehouse_list List all warehouses in a Fabric workspace with their metadata and connection details. Read workspace_capacity_info List Fabric capacities with their SKU, state, and region. Includes capacity optimization tips. Read workspace_list List all Fabric workspaces you have access to with their IDs, types, and capacity assignments. Read workspace_list_items List all items in a Fabric workspace, optionally filtered by type (Lakehouse, Warehouse,

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Force Fabric MCP Server

Can an AI agent delete data through the Force Fabric MCP Server MCP server? +

Yes. The Force Fabric MCP Server server exposes 1 destructive tools including auth_logout. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Force Fabric MCP Server? +

The Force Fabric MCP Server server has 1 write tools including semantic_model_auto_optimize. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Force Fabric MCP Server.

How many tools does the Force Fabric MCP Server MCP server expose? +

33 tools across 4 categories: Destructive, Execute, Read, Write. 17 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on Force Fabric MCP Server? +

Register the Force Fabric MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Force Fabric MCP Server tool call.

Deterministic rules across all 33 Force Fabric MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

33 Force Fabric MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.