kdbai_query_data · KDB AI MCP Server MCP: Risk & Policy

WHAT IT DOES

What kdbai_query_data does on KDB AI MCP Server

AI agents invoke kdbai_query_data to trigger actions in KDB AI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why kdbai_query_data needs a policy

The name suggests querying data, which could be read-only. However, 'query' in a vector/time-series database context (KDB.AI) can involve executing arbitrary query expressions that may have side effects beyond simple reads. Given the empty description, I cannot confirm it is purely read-only. The most likely interpretation is Execute (running a query), but it could be Read.

From the tool's definition Tool name 'kdbai_query_data' — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kdbai_query_data Rate-limited

kdbai_query_data stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kdbai_query_data": {
      "limits": [
        {
          "counter": "kdbai_query_data_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches KDB AI MCP Server, so you can run agents against it safely.

FAQ

Questions about kdbai_query_data

What does the kdbai_query_data tool do? +

kdbai_query_data. It is categorised as a Execute tool in the KDB AI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kdbai_query_data? +

Register the KDB AI MCP Server MCP server in PolicyLayer and add a rule for kdbai_query_data: 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.

What risk level is kdbai_query_data? +

kdbai_query_data is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit kdbai_query_data? +

Yes. Add a rate_limit block to the kdbai_query_data 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.

How do I block kdbai_query_data completely? +

Set action: deny in the PolicyLayer policy for kdbai_query_data. 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.

What MCP server provides kdbai_query_data? +

kdbai_query_data 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.