kdb_insert · KDB MCP Service MCP: Risk & Policy

WHAT IT DOES

What kdb_insert does on KDB MCP Service

AI agents use kdb_insert to create or update resources in KDB MCP Service — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KDB MCP Service environment.

WHY IT NEEDS A POLICY

Why kdb_insert needs a policy

kdb_insert creates new records in a database table, which is a reversible write operation. It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). Severity is medium because inserting incorrect or malicious data into a financial/time-series database could corrupt analytics or trigger downstream business logic, but the operation itself is reversible via update or delete.

From the tool's definition Tool name 'kdb_insert' and description 'Insert data into a KDB+ table' indicate data creation/modification into a KDB+ database. The server description confirms 'full CRUD operations' including insert capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kdb_insert Rate-limited

kdb_insert stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kdb_insert": {
      "limits": [
        {
          "counter": "kdb_insert_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 MCP Service, so you can run agents against it safely.

FAQ

Questions about kdb_insert

What does the kdb_insert tool do? +

Insert data into a KDB+ table. It is categorised as a Write tool in the KDB MCP Service MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on kdb_insert? +

Register the KDB MCP Service MCP server in PolicyLayer and add a rule for kdb_insert: 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 MCP Service. Nothing to install.

What risk level is kdb_insert? +

kdb_insert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kdb_insert? +

Yes. Add a rate_limit block to the kdb_insert 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 kdb_insert completely? +

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

kdb_insert is provided by the KDB MCP Service MCP server (riteshsonawala/kdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.