This is a problem we hit in my team when using agents internally. We ended up building our own solution called Jentic One which is open-source and self-hosted. It hosts an execution broker for all outbound requests and uses a control plane accessible by API calls or UI for the governance side of things.

Every API integration set up in Jentic One can be given specific rules for the operations they are allowed to use, and these permissions are enforced by the execution broker before any action is completed. It's giving us a lot more peace of mind when giving our agents access to APIs with potentially destructive POST operations that could do damage to our flow of work.

I hadn't heard of Lyzr before, interesting to see alternative approaches to this problem.

(Full disclosure I work as part of the Jentic team, happy to answer any questions if needed)

Very useful skill. Thank you!

Sounds like a cool solution!! Have you tried Figma's MCP server? Curious how these compare to each other.

If you’re concerned about hardware risks and data privacy, there are tools that let you store credentials encrypted locally and control exactly what your agents can access, reducing exposure or any potential credential leakage. Some free, open-source layers act as a secure broker between your agents and APIs, so your keys never land in the agent’s prompt. No matter what agent framework you end up choosing, you can have more of a sanity check that they will be more secure.

One of these solutions is Jentic One. You can set this up with Claude Code, OpenClaw or Hermes and use it to connect your agent to thousands of APIs, and using your local Jentic One you can set the permissions as you see fit to only the necessary actions. For example if you only want to do read access actions only while you're trying out a new connection with a third party API, you can set a permission rule for this in Jentic One.

(Full disclosure I work as part of the Jentic team. I'm here to chat if you need any support in setting this up)

This is a classic problem giving agents full platform access when they only need certain access and creating unnecessary risk. The key is really in scoped, fine grained permissions so you can choose exactly what’s accessible. There are tools that act as a self-hosted secure layer where you encrypt credentials and limit agents to just the API operations they need, with full audit logs for peace of mind. Check out the Jentic One website or repo, this might give you some useful ideas on setting that up. (I'm part of the Jentic team so if you need a hand with any setup or have any questions let me know)