lakehouse_list

THE RISK

Low Risk

Why lakehouse_list needs a policy

This tool retrieves and queries existing metadata about Lakehouses within a Fabric workspace. It has no side effects—it does not create, modify, delete, or execute operations. The action is purely informational, fitting the 'Read' category for data retrieval operations.

From the tool's definition Tool name 'lakehouse_list' and description 'List all lakehouses in a Fabric workspace with their metadata, SQL endpoint status, and OneLake paths' indicate a retrieval/query operation that returns information without modifying or deleting data.

Documented attack patterns abuse exactly the kind of access lakehouse_list gives an agent:

POLICY

How to control lakehouse_list

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_list:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lakehouse_list": {}
  }
}

lakehouse_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Force Fabric MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Force Fabric MCP Server tools

Destructive auth_logout Logout from Microsoft Fabric and clear cached credentials. 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 a 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).

All 33 Force Fabric MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about lakehouse_list

What does the lakehouse_list tool do? +

List all lakehouses in a Fabric workspace with their metadata, SQL endpoint status, and OneLake paths. It is categorised as a Read tool in the Force Fabric MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lakehouse_list? +

Register the Force Fabric MCP Server MCP server in PolicyLayer and add a rule for lakehouse_list: 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.

What risk level is lakehouse_list? +

lakehouse_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lakehouse_list? +

Yes. Add a rate_limit block to the lakehouse_list 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.

How do I block lakehouse_list completely? +

Set action: deny in the PolicyLayer policy for lakehouse_list. 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.

What MCP server provides lakehouse_list? +

lakehouse_list 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.

Enforce policy on every Force Fabric MCP Server tool call.

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.

CHECK YOUR STACK →