Debug function to check various API endpoints for lakehouse contents including files and items.
AI agents call debug_lakehouse_contents 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 queries and inspects lakehouse contents via API endpoints to help with debugging. It is fundamentally a Read operation—it retrieves information about files and items for diagnostic purposes. The low severity reflects that while it may expose data about lakehouse structure, it cannot modify, delete, execute arbitrary operations, or cause financial impact.
From the tool's definition The tool is described as a 'Debug function to check various API endpoints for lakehouse contents including files and items.' The verbs 'check' and 'debug' indicate it retrieves and inspects data without modification.
Attacks that exploit this kind of access
Debug function to check various API endpoints for lakehouse contents including files and items. 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 debug_lakehouse_contents: 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.
debug_lakehouse_contents 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 debug_lakehouse_contents 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 debug_lakehouse_contents. 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.
debug_lakehouse_contents 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 →