AI agents can delete your DB, push broken code, or burn $500 overnight, you find out after. This is what is capable of: š“ Permission Gate: dangerous tool calls blocked before execution, Telegram Approve/Deny, agent waits š° Budget Guard: hard daily spend cap per agent, automatic kill switch š Activity Feed: every action logged, exportable as audit trail for clients One env variable. Works with Claude Code, OpenClaw, LangChain, CrewAI, AutoGen. Deterministic. No ML in the safety path.
No reviews yetBe the first to leave a review for Daedalab
Maker
š
Hey PH š
Three months ago an agent I was running went into a loop overnight and burned $200 in API credits. Last month a different one tried to run "git push --force" on production infrastructure.
I couldn't find anything that blocked dangerous actions at the tool call level; not at the prompt level, not with a better system message. So I built Daedalab.
It's a proxy that sits between your agents and the LLM providers. You change one environment variable. From that moment, every tool call gets classified in real time:
š¢ Safe ā passes through
š“ Critical (delete_file, git_push, send_email to real recipients) ā blocked, Telegram notification fires, agent waits for your Approve or Deny
The classification is deterministic, I read the function name from the tool call JSON directly. No LLM in the safety path. delete_file is always blocked. Every time. No exceptions, no hallucinations about whether something is dangerous.
Works with Claude Code (API key), OpenClaw, LangChain, CrewAI, AutoGen; anything that exposes a configurable base_url.
Happy to answer anything technical about how the proxy works. And yes, I know the irony of launching an agent safety tool the same week the terraform destroy incident went viral.