Calvin Seward

Plan to link your LLM to your production database? What could possibly go wrong?

Your read-only transaction isn't safe. An LLM can be tricked into committing a `TRUNCATE` command.

Plan to link your LLM to your production database? What could possibly go wrong?
#1about 3 minutes

Why traditional database search interfaces are frustrating

Many applications are just interfaces to databases, but traditional search filters often fail to capture complex user intent.

#2about 4 minutes

How to connect an LLM to a database using tools

An LLM can be given a "tool" with a defined JSON schema, allowing it to translate natural language questions into SQL queries.

#3about 8 minutes

Demonstrating prompt and SQL injection attacks

Allowing an LLM to execute raw SQL creates vulnerabilities for prompt injection to leak data and SQL injection to bypass read-only restrictions.

#4about 5 minutes

Securing database access with a model context protocol server

An MCP server acts as an intermediary that only executes whitelisted, parameterized queries, which drastically reduces the attack surface.

#5about 2 minutes

Performing safe database writes through an LLM

The MCP server enables safe write operations, like creating a reservation, by exposing specific tools instead of general SQL access.

#6about 5 minutes

Best practices for designing robust LLM database tools

Improve your MCP server's performance and reliability with caching, tool organization, specific outcome mapping, and clear error handling.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Articles

View all articles

From learning to earning

Jobs that call for the skills explored in this talk.