{
  "id": 13970980,
  "title": "Guarding a support agent's tool calls: provenance, a customer's yes, written gates and a backend that teaches",
  "url": "https://urgent.news/2026/10/12/guarding-a-support-agents-tool-calls-provenance-a-customers-yes",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-12T14:00:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/mxkuzn/guarding-a-support-agents-tool-calls-provenance-a-customers-yes-written-gates-and-a-backend-2o77"
  },
  "original_language": "en",
  "account": "An LLM agent with tools can propose actions, such as cancelling an order, but a guard decides whether to allow, deny, or escalate. The guard checks provenance, ensuring the order ID belongs to the customer, and executes a policy that the customer can cancel only their own orders. If the order is delivered, the guard denies the cancellation. The guard stores decisions for traceability.",
  "summary": "An LLM agent with tools is a model whose outputs have side effects. \"Cancel order #W9034102\" is a fine thing to say and a bad thing to do when the order belongs to someone else and the instruction came from a note inside a tool result. This post puts solvi.Guard between a retail support agent and its tools, adds a written policy as hard gates and a knowledge store that learns what the backend…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}