kdbai_list_tables
AI agents call kdbai_list_tables to retrieve information from KDB AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing tables is a read-only query operation that retrieves schema information. It has no side effects, does not execute code, modify data, or delete anything. The blast radius if misused is minimal—an attacker gains only knowledge of available tables, not access to sensitive data within them (unless combined with subsequent query tools). Low severity reflects the informational nature of the operation.
From the tool's definition Tool name 'kdbai_list_tables' indicates listing operation. Description is empty, but sibling tools like 'kdbai_list_databases' and the stated server purpose (vector database operations) confirm this retrieves metadata without modification.
Attacks that exploit this kind of access
kdbai_list_tables. It is categorised as a Read tool in the KDB AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KDB AI MCP Server MCP server in PolicyLayer and add a rule for kdbai_list_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 KDB AI MCP Server. Nothing to install.
kdbai_list_tables 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 kdbai_list_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.
Set action: deny in the PolicyLayer policy for kdbai_list_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.
kdbai_list_tables is provided by the KDB AI MCP Server MCP server (kxsystems/kdbai-mcp-server). 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 →