HeimdaLLMο
Pronounced [ΛhaΙͺm.dΙl.Ιm] or HEIM-dall-em
HeimdaLLM is a robust static analysis framework for validating that LLM-generated structured output is safe. It currently supports SQL.
In simple terms, it helps makes sure that AI wonβt wreck your systems.

Consider the following natural-language database query:
how much have i spent renting movies, broken down by month?
From this query (and a little bit of context), an LLM can produce the following SQL query:
SELECT
strftime('%Y-%m', payment.payment_date) AS month,
SUM(payment.amount) AS total_amount
FROM payment
JOIN rental ON payment.rental_id=rental.rental_id
JOIN customer ON payment.customer_id=customer.customer_id
WHERE customer.customer_id=:customer_id
GROUP BY month
LIMIT 10;
But how can you ensure the LLM-generated query is safe and that it only accesses authorized data?
HeimdaLLM performs static analysis on the generated SQL to ensure that only certain
columns, tables, and functions are used. It also automatically edits the query to add a
LIMIT
and to remove forbidden columns. Lastly, it ensures that there is a column
constraint that would restrict the results to only the userβs data.
It does all of this locally, without AI, using good olβ fashioned grammars and parsers:
β
Ensuring SELECT statement...
β
Resolving column and table aliases...
β
Allowlisting selectable columns...
β
Removing 2 forbidden columns...
β
Ensuring correct row LIMIT exists...
β
Lowering row LIMIT to 10...
β
Checking JOINed tables and conditions...
β
Checking required WHERE conditions...
β
Ensuring query is constrained to requester's identity...
β
Allowlisting SQL functions...
β
strftime
β
SUM
The validated query can then be executed:
month |
total_amount |
2005-05 |
4.99 |
2005-06 |
22.95 |
2005-07 |
100.78 |
2005-08 |
87.82 |
Want to get started quickly? π Quickstart.