AI agents call table_details to retrieve information from LanceDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about a table structure without modifying, deleting, or executing operations on the underlying data. It is a read-only operation consistent with the 'Read' category (get, fetch operations). The blast radius is minimal as it only returns informational metadata about table schema/structure.
From the tool's definition Tool name 'table_details' and description 'Get the details of a LanceDB table' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access table_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LanceDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for table_details:
{
"version": "1",
"default": "deny",
"tools": {
"table_details": {}
}
}table_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the details of a LanceDB table. It is categorised as a Read tool in the LanceDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LanceDB MCP Server MCP server in PolicyLayer and add a rule for table_details: 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 LanceDB MCP Server. Nothing to install.
table_details 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 table_details 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 table_details. 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.
table_details is provided by the LanceDB MCP Server MCP server (lancedb/lancedb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LanceDB 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.
3 LanceDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.