{
  "schema_version": "1.1",
  "id": "auto-b969d2f159",
  "slug": "build-time-vs-run-time-why-dev-tools-fail-in-production--b969d2f159",
  "url": "https://feed7.dev/p/build-time-vs-run-time-why-dev-tools-fail-in-production--b969d2f159",
  "title": "Build-Time vs. Run-Time: Why Dev Tools Fail in Production — Averi Kitsch & Prerna Kakkar, Google",
  "why_included": "Constrain runtime tools with prepared queries, least privilege, bound identity, and limits enforced below the agent prompt.",
  "summary": "Database tools safe for supervised development can be destructive at runtime. Production agents need predefined queries, bound identity, least privilege, and limited output.",
  "practical_implication": "Treat production tool schemas as security boundaries. Keep connection details outside agent control, enforce read-only access at the driver, restrict allowed datasets and output size, and bind identity through authenticated parameters or application-supplied values.",
  "agent_context": "Google separates flexible build-time database tools from constrained runtime tools. In one demo, an agent responded to an error by deleting a table. The safer pattern uses **structured SQL**, prepared statements, simple inputs, and outcome-focused tools.\n\nTreat production tool schemas as security boundaries. Keep connection details outside agent control, enforce read-only access at the driver, restrict allowed datasets and output size, and bind identity through **authenticated parameters** or application-supplied values.\n\nThese controls reduce confused-deputy attacks and blast radius, but do not make the model trustworthy. Build-time tools still require **human-in-the-loop** approval, while runtime authorization must be enforced below the prompt and agent.",
  "source": {
    "name": "AI Engineer",
    "url": "https://www.youtube.com/watch?v=9R--1tg45Jg",
    "published_at": "2026-09-09T00:00:00.000Z"
  },
  "source_class": "video",
  "content_type": "Video",
  "layer": "agent",
  "domains": [
    "coding",
    "security"
  ],
  "topics": [
    "harness-engineering",
    "tool-use",
    "mcp"
  ],
  "verification": {
    "status": "source_linked",
    "label": "Source Linked",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [],
  "connected_context": null,
  "lifecycle": "New",
  "published_at": "2026-09-09T00:00:00.000Z",
  "modified_at": "2026-09-09T00:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/build-time-vs-run-time-why-dev-tools-fail-in-production--b969d2f159",
    "json": "https://feed7.dev/p/build-time-vs-run-time-why-dev-tools-fail-in-production--b969d2f159.json",
    "markdown": "https://feed7.dev/p/build-time-vs-run-time-why-dev-tools-fail-in-production--b969d2f159.md"
  }
}