This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
valv
Give AI agents safe, scoped access to your database
Most agents get one god-mode DB connection, valv gives every user their own. A customer asks your support agent "where's my order?" With a raw connection, that query could read every other customer's rows too. With valv, you set programmatic per-user permissions once, every query is validated and scoped to the caller, and no raw SQL ever hits your DB. Ships as an MCP server or a TypeScript library.
Giving an agent access to your database is one of the most powerful ways to gain insights over your customers, product or even to debug issues. But every time I connect an agent to a real database you have to handle the same things:
As soon as you want to give this capability to other people as well this becomes a messy construct of prompting and DB rules to handle. One malicious prompt, one uncaught query, and the agent could read or wipe data it was never meant to touch.
Valv solves this issue:
You define programmatic, per-user permissions in code. From then on, every query the agent runs is validated and scoped to the user before it ever reaches your DB. No raw SQL and no god-mode connection.
Use it...
...as an MCP server, so any MCP client can query your data safely
...as a TypeScript library, dropped straight into your own app. This also lets you expose an MCP server for others to use.
Same safe layer, wherever your agent runs.
It's live today as an early release that we are already using ourselves. We would love to hear your feedback, especially from anyone who's tried (and struggled) to give an agent real data access. What broke for you? What would you want valv to handle next?
How does this actually hold up with more complex queries like joins or stored procedures? Seems like intercepting and rewriting everything could get messy fast, curious what the limits are in practice.
The per-user permission setup felt surprisingly painless, and I like that it blocks raw SQL entirely instead of just hoping nothing slips through.
Curious how this plays with Postgres row level security that's already in place — do you end up wrapping those policies or replacing them entirely?
How does it actually validate the SQL when it's coming from an LLM, since the model can pretty much construct any query it wants?
About valv on Product Hunt
“Give AI agents safe, scoped access to your database”
valv was submitted on Product Hunt and earned 18 upvotes and 9 comments, placing #22 on the daily leaderboard. Most agents get one god-mode DB connection, valv gives every user their own. A customer asks your support agent "where's my order?" With a raw connection, that query could read every other customer's rows too. With valv, you set programmatic per-user permissions once, every query is validated and scoped to the caller, and no raw SQL ever hits your DB. Ships as an MCP server or a TypeScript library.
valv was featured in Developer Tools (515.4k followers), Artificial Intelligence (473.1k followers), GitHub (41.3k followers) and Data & Analytics (5.7k followers) on Product Hunt. Together, these topics include over 208.1k products, making this a competitive space to launch in.
Who hunted valv?
valv was hunted by Joshua Knauber. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how valv stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Joshua Knauber
Hey Product Hunt 👋
Giving an agent access to your database is one of the most powerful ways to gain insights over your customers, product or even to debug issues. But every time I connect an agent to a real database you have to handle the same things:
As soon as you want to give this capability to other people as well this becomes a messy construct of prompting and DB rules to handle. One malicious prompt, one uncaught query, and the agent could read or wipe data it was never meant to touch.
Valv solves this issue:
You define programmatic, per-user permissions in code. From then on, every query the agent runs is validated and scoped to the user before it ever reaches your DB. No raw SQL and no god-mode connection.
Use it...
...as an MCP server, so any MCP client can query your data safely
...as a TypeScript library, dropped straight into your own app. This also lets you expose an MCP server for others to use.
Same safe layer, wherever your agent runs.
It's live today as an early release that we are already using ourselves. We would love to hear your feedback, especially from anyone who's tried (and struggled) to give an agent real data access. What broke for you? What would you want valv to handle next?
Thanks for checking it out 🙏