#1616
[Feature]: Guardrails native to MongoDB
Is your feature request related to a problem?
We were unable to execute the “hoop connect” command on a connection to MongoDB resources when the Guardrails were configured.
Describe the solution you'd like
Native Guardrails to MongoDB.
Describe alternatives you've considered
No response
Priority
Medium - Would improve my workflow
Use Case
Using MongoDB connections via rule packages or custom Guardails in the IDE
Mockups or Examples
No response
Additional Context
No response
Contribution
- I would be willing to submit a PR to implement this feature
Code of Conduct
- I agree to follow this project's Code of Conduct
Database-native guardrails are powerful because the policy follows the action to the place where damage can happen. The key is returning an explanation the agent and operator can both use.
We are working on the same contract in MartinLoop: what was requested, what policy decided, what executed, and what evidence remains afterward.
Would you make guardrail decisions visible in the query response or only in an audit trail? I would appreciate your take, and the repo is here if our receipt model is useful: https://github.com/Keesan12/martin-loop