AI agents call query_table 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.
Based on the tool name and server context (a document retrieval system with ingest, retrieve, and table details operations), query_table most likely retrieves or queries data from stored documents without modification. The absence of 'delete', 'drop', 'update', or 'execute' language, combined with the retrieval-focused purpose of the LanceDB server, indicates a Read operation.
From the tool's definition Tool name 'query_table' suggests querying/retrieving data from a table. The server description emphasizes 'retrieve' as one of three core functions. No description provided for this specific tool.
Documented attack patterns abuse exactly the kind of access query_table 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 query_table:
{
"version": "1",
"default": "deny",
"tools": {
"query_table": {}
}
} query_table 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.
query_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 query_table: 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.
query_table 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 query_table 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 query_table. 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.
query_table 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.