Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: EnrichMCP – A Python ORM for Agents

github.com

Post reply on HN
Print view View original

31–35 of 35 posts

Re: Show HN: EnrichMCP – A Python ORM for Agents

#31

Post by Too »

simba-k wrote: post #7
polskibus wrote: post #6

This looks very interesting but I’m not sure how to use it well. Would you mind sharing some prompts that use it and solve a real problem that you encountered ?

Imagine you're building a support agent for DoorDash. A user asks, "Why is my order an hour late?" Most teams today would build a RAG system that surfaces a help center article saying something like, "Here are common reasons orders might be delayed." That doesn't actually solve the problem. What you really need is access to internal systems. The agent should be able to look up the order, check the courier status, pul…

Do you have a less hypothetical example to share?

Just a basic prompt that makes use of this server and how it responds. Or a simple agent conversation that continues successfully beyond 5 roundtrips.

Re: Show HN: EnrichMCP – A Python ORM for Agents

#34

Post by TZubiri »

simba-k wrote: post #25
TZubiri wrote: post #19

Earlier quoted context omitted.

Cool. Can you give the agent a db user with restricted read permissions? Also, generic db question, but can you protect against resource overconsumption? Like if the junior/agent makes a query with 100 joins, can a marshall kill the process and time it out?

Yeah to restricted read, still a lot of API work to do here and we're a bit blocked by MCP itself changing its auth spec (was just republished yesterday). If you use the lower-level enrichMCP API (without SQLAlchemy) you can fully control all retrieval logic and add things like rate limiting, not dissimilar to how you'd solve this problem with a traditional API.

You could do this out of the MCP protocol, just by making a SQL user account with restricted privileges. I'm assuming at some point you have to give the mcp orm credentials. I think it's easier and more maintainable to just add a doc page tutorial showing how to do it instead of making it part of the dependency. It also reduces the scope of the library.
Post reply on HN