Lists all lakehouses in a specified Fabric workspace.
AI agents call list_fabric_lakehouses to retrieve information from Semantic Model MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/enumeration operation that retrieves information about lakehouses without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only discover what lakehouses exist in a workspace, which is a read-only side effect. Classified as Read/low.
From the tool's definition Tool name 'list_fabric_lakehouses' and description 'Lists all lakehouses in a specified Fabric workspace' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Lists all lakehouses in a specified Fabric workspace. It is categorised as a Read tool in the Semantic Model MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Semantic Model MCP Server MCP server in PolicyLayer and add a rule for list_fabric_lakehouses: 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 Semantic Model MCP Server. Nothing to install.
list_fabric_lakehouses is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_fabric_lakehouses 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 list_fabric_lakehouses. 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.
list_fabric_lakehouses is provided by the Semantic Model MCP Server MCP server (nahtheking/semantic-model-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →