Show HN: Focus on approving agent actions and managing team MCP access
Check proposed AI agent outputs and actions against policy before execution. Get allow, block, rewrite, or escalate decisions with a reason and trace ID.
Summary not yet generated for this article.
Original Text
1. i use to work at ai agent testing ocmany i saw Agent is actually filming every day so I think to myself, why don't we just build Godrail approval so it is not filming in production? We would have a set of policies. For example if anything violates that, it would be stopped. It could be like a spending cap and all, like a destructive comment.
2. The use case is very flexible so the manager could have access here and then be granted some permission on a different tool code that I had on their server. For SAK dashboard we have a live demo. Everything is really easy to integrate, just a few lines.
Currently I wanted to validate this by checking the pooling signal. There is a lot of governance popping up but I just wanna validate.
Technically they will hook this up to their agent or any workflow. Whenever there was a proposed tool call or something like that, it will be escalated to the user, do a policy check, and it signs the receipt.
Comments (0 of ) ⌛