Low Risk

discover_lakehouse_tables

List all tables in a Lakehouse with their names and formats.

How to control discover_lakehouse_tables ↓

What discover_lakehouse_tables does on Fabric Ontology MCP Server

AI agents call discover_lakehouse_tables to retrieve information from Fabric Ontology MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why discover_lakehouse_tables needs a policy

This tool performs a read-only query operation that retrieves metadata about existing Lakehouse tables. It does not create, modify, delete, or execute any operations; it simply enumerates available resources. Blast radius is minimal—exposure only allows an AI agent to discover what tables exist, not to alter them or trigger external actions.

From the tool's definition Tool name contains 'discover' and description states 'List all tables' — both indicate data retrieval with no modification or side effects.

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

How to control discover_lakehouse_tables

PolicyLayer is an MCP gateway — it sits between your AI agents and Fabric Ontology MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for discover_lakehouse_tables:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "discover_lakehouse_tables": {}
  }
}

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

  1. Create a free account and register Fabric Ontology MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about discover_lakehouse_tables

What does the discover_lakehouse_tables tool do? +

List all tables in a Lakehouse with their names and formats. It is categorised as a Read tool in the Fabric Ontology MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on discover_lakehouse_tables? +

Register the Fabric Ontology MCP Server MCP server in PolicyLayer and add a rule for discover_lakehouse_tables: 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 Fabric Ontology MCP Server. Nothing to install.

What risk level is discover_lakehouse_tables? +

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

Can I rate-limit discover_lakehouse_tables? +

Yes. Add a rate_limit block to the discover_lakehouse_tables 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 discover_lakehouse_tables completely? +

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

discover_lakehouse_tables is provided by the Fabric Ontology MCP Server MCP server (tmdaidevs/ontology-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 Fabric Ontology MCP Server tool call.

Start from Fabric Ontology 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.

45 Fabric Ontology 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.