An0n_Jon

5 ms·

1.
Kill Your MCP Servers(anonjon.substack.com)
1 points by An0n_Jon 5mo ago|0 comments
2.
by An0n_Jon 5mo ago
Yeah, this is the reasons why Orloj has built in policies which are applied to your resources and managed at the runtime level. This way you can allow only certain tool usage per agent for a more fine grained setup.
3.
by An0n_Jon 5mo ago
Yeah the governance is also built into Orloj as well as applied policies. More so acting as guardrails at the runtime level. Ill take a look at agentveil and would love to know your thoughts on Orloj as well.
4.
by An0n_Jon 5mo ago
Yeah, agreed it feels like overkill keeping the resource running if nothing is calling it. Even with read only you still have the issue with wasted resources but I get what you mean. Orloj is a runtime with policies you apply as guardrails
5.
The way every agent framework handles MCP is a latent security problem
2 points by An0n_Jon 5mo ago|6 comments
6.
by An0n_Jon 6mo ago
Yep, totally agree. And Orloj has this built in. Tracks the entire lifecycle of your tasks through traces in real time so you can audit why everything happened good/bad. During your task you can see how many tokens each call used (inpu
7.
by An0n_Jon 6mo ago
Definitely understand the perspective. I think with all software in general there will be a time where you need to adapt to changing technologies/architectures which is why we open sourced the core so we can have contributors build off
8.
by An0n_Jon 6mo ago
Didn't realize the Czechs had so many...The story about the clockmaker on the Prague one was interesting. The king trying to blind him so he could never make another for anyone else...
9.
by An0n_Jon 6mo ago
This is where the governance layer of Orloj fits in. You create policies and attach them to agents/tools which are all governed at runtime. These policies could be token guardrails, tool authority, etc. You can then check all of the tr
10.
by An0n_Jon 6mo ago
It depends on what you're trying to build to be honest. For simple tasks Orloj can be a little overkill but it really starts shining when you are trying to setup large task flows that need many agents/tools/policies. Working
11.
by An0n_Jon 6mo ago
Yes! We visited The Prague Orloj 2 years ago and it's amazing engineering. That's why we named it after it, for how it's coordinating and orchestrating so many complex mechanisms. (for anyone wondering it's pronounced O
12.
Show HN: Orloj – agent infrastructure as code (YAML and GitOps)(github.com)
20 points by An0n_Jon 6mo ago|12 comments
13.
by An0n_Jon 6mo ago
This is interesting. It says agents self register...How do agents find this? And why would they decide to create a profile? Wouldn't they be costing their owner tokens to do this?
14.
by An0n_Jon 6mo ago
Hi HN — I built kroot to help debug Kubernetes failures by tracing dependencies between resources. Instead of only showing symptoms (CrashLoopBackOff, etc), it builds a dependency graph of cluster resources and tries to answer: "Why di
15.
Show HN: Kroot – dependency-graph root cause analysis for Kubernetes(github.com)
1 points by An0n_Jon 6mo ago|1 comments