kdbai_table_info
AI agents call kdbai_table_info 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.
This tool appears to query or retrieve metadata about a table structure in KDB.AI—a read-only operation with no capability to modify, delete, or execute arbitrary code. The lack of an explicit description lowers confidence slightly, but the consistent naming convention of sibling informational tools and the '_info' suffix make it clear this is an information retrieval function.
From the tool's definition Tool name 'kdbai_table_info' indicates it retrieves information about tables. Sibling tools like 'kdbai_database_info', 'kdbai_list_databases', and 'kdbai_list_tables' are all read-only query operations.
Attacks that exploit this kind of access
kdbai_table_info. 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_table_info: 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_table_info 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_table_info 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_table_info. 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_table_info 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 →