---
schema: 1
type: video
title: AI Agents Don't Read Your Policy Docs. They Hit Your APIs — Gravitee
description: >-
  You can write all the rules you want in a markdown file. Your agent can still
  call the API. Sam, CTO at Gravity, skips the slides and runs five live
  scenarios against a hotel-booking agent to show why governance belongs in the
  infrastructure, not in the agent's instructions. Running on the Gravity
  Gateway with a Databricks backend, Sonnet and Groq, he shows the gateway
  blocking a destructive "delete all bookings" tool call, stopping an attempt to
  pull every guest's personal data, rate-limiting a buggy agent that fires the
  same request eight times, serving repeated questions from a semantic cache,
  and rejecting an oversized prompt before it ever reaches the LLM. He also
  covers telemetry across your agents, decoupling from any one hyperscaler,
  trimming bloated MCP tool lists, and shadow AI on employee laptops. In this
  talk: • Why prompts and policy docs can't enforce what agents do • Blocking
  destructive tool calls and data exfiltration at the gateway • Rate limits,
  semantic caching and token limits that cut cost • Observability, decoupling
  from vendors, and trimming MCP tools SPEAKER Sam, CTO, Gravity CHAPTERS 0:00
  Intro 0:52 Agents without governance 1:32 Move policy to the gateway 2:57 Demo
  1: Blocking destructive tools 4:57 Demo 2: Stopping data exfiltration 6:56
  Demo 3: Runaway repeat requests 8:21 Demo 4: Semantic caching 11:01 Demo 5:
  Blocking oversized prompts 12:21 Expensive agent habits 15:01 Avoiding vendor
  lock-in 15:41 Trimming MCP tools 16:16 Shadow AI 16:56 Wrap-up Recorded at the
  AI Engineer World's Fair 2026 in San Francisco. Subscribe for more talks from
  the engineers building with AI. AI Engineer: https://ai.engineer YouTube:
  https://www.youtube.com/@aiDotEngineer X: https://x.com/aiDotEngineer
  LinkedIn: https://www.linkedin.com/company/aidotengineer/ #AIAgents
  #AIGovernance #AIEngineer
canonical: >-
  https://liquidgold.cc/channel/aidotengineer/explore/video/ai-agents-don-t-read-your-policy-docs-they-hit-your-9a7bdf76013b
markdown: >-
  https://liquidgold.cc/channel/aidotengineer/video/ai-agents-don-t-read-your-policy-docs-they-hit-your-9a7bdf76013b.md
llms: null
parent: 'https://liquidgold.cc/channel/aidotengineer.md'
channel: aidotengineer
updated: '2026-10-23T22:19:22.243Z'
language: null
children: []
videoId: 7v2myBde05o
durationSeconds: 1070
publishedAt: '2026-10-10T21:00:39.000Z'
searchChunks:
  - ordinal: 0
    text: null
    startSeconds: 57
    endSeconds: 67
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=57'
    heldReason: rights
  - ordinal: 1
    text: null
    startSeconds: 67
    endSeconds: 102
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=67'
    heldReason: rights
  - ordinal: 2
    text: null
    startSeconds: 113
    endSeconds: 179
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=113'
    heldReason: rights
  - ordinal: 3
    text: null
    startSeconds: 179
    endSeconds: 189
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=179'
    heldReason: rights
  - ordinal: 4
    text: null
    startSeconds: 189
    endSeconds: 298
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=189'
    heldReason: rights
  - ordinal: 5
    text: null
    startSeconds: 298
    endSeconds: 310
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=298'
    heldReason: rights
  - ordinal: 6
    text: null
    startSeconds: 418
    endSeconds: 430
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=418'
    heldReason: rights
  - ordinal: 7
    text: null
    startSeconds: 430
    endSeconds: 509
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=430'
    heldReason: rights
  - ordinal: 8
    text: null
    startSeconds: 521
    endSeconds: 665
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=521'
    heldReason: rights
  - ordinal: 9
    text: null
    startSeconds: 665
    endSeconds: 676
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=665'
    heldReason: rights
  - ordinal: 10
    text: null
    startSeconds: 676
    endSeconds: 744
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=676'
    heldReason: rights
  - ordinal: 11
    text: null
    startSeconds: 755
    endSeconds: 902
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=755'
    heldReason: rights
  - ordinal: 12
    text: null
    startSeconds: 902
    endSeconds: 913
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=902'
    heldReason: rights
  - ordinal: 13
    text: null
    startSeconds: 913
    endSeconds: 946
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=913'
    heldReason: rights
  - ordinal: 14
    text: null
    startSeconds: 979
    endSeconds: 990
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=979'
    heldReason: rights
  - ordinal: 15
    text: null
    startSeconds: 1022
    endSeconds: 1034
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=1022'
    heldReason: rights
  - ordinal: 16
    text: null
    startSeconds: 310
    endSeconds: 418
    watch: 'https://liquidgold.cc/watch/7v2myBde05o?t=310'
    heldReason: rights
---


# AI Agents Don't Read Your Policy Docs. They Hit Your APIs — Gravitee

You can write all the rules you want in a markdown file. Your agent can still call the API. Sam, CTO at Gravity, skips the slides and runs five live scenarios against a hotel-booking agent to show why governance belongs in the infrastructure, not in the agent's instructions. Running on the Gravity Gateway with a Databricks backend, Sonnet and Groq, he shows the gateway blocking a destructive "delete all bookings" tool call, stopping an attempt to pull every guest's personal data, rate-limiting a buggy agent that fires the same request eight times, serving repeated questions from a semantic cache, and rejecting an oversized prompt before it ever reaches the LLM. He also covers telemetry across your agents, decoupling from any one hyperscaler, trimming bloated MCP tool lists, and shadow AI on employee laptops. In this talk: • Why prompts and policy docs can't enforce what agents do • Blocking destructive tool calls and data exfiltration at the gateway • Rate limits, semantic caching and token limits that cut cost • Observability, decoupling from vendors, and trimming MCP tools SPEAKER Sam, CTO, Gravity CHAPTERS 0:00 Intro 0:52 Agents without governance 1:32 Move policy to the gateway 2:57 Demo 1: Blocking destructive tools 4:57 Demo 2: Stopping data exfiltration 6:56 Demo 3: Runaway repeat requests 8:21 Demo 4: Semantic caching 11:01 Demo 5: Blocking oversized prompts 12:21 Expensive agent habits 15:01 Avoiding vendor lock-in 15:41 Trimming MCP tools 16:16 Shadow AI 16:56 Wrap-up Recorded at the AI Engineer World's Fair 2026 in San Francisco. Subscribe for more talks from the engineers building with AI. AI Engineer: https://ai.engineer YouTube: https://www.youtube.com/@aiDotEngineer X: https://x.com/aiDotEngineer LinkedIn: https://www.linkedin.com/company/aidotengineer/ #AIAgents #AIGovernance #AIEngineer

Canonical: https://liquidgold.cc/channel/aidotengineer/explore/video/ai-agents-don-t-read-your-policy-docs-they-hit-your-9a7bdf76013b · Channel: [AI Engineer](https://liquidgold.cc/channel/aidotengineer.md)

> Search chunk text is held until public-source provenance is verified.

## Document chunks

> Missing: no stored document chunks are available.
