We’ve been building visual rule engines (clear interfaces + API endpoints that map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.
The result is a surprisingly useful policy/gating layer– these tables let your team:
- Write multi-factor, exception-friendly policies (e.g. deny rm -rf / when --force; allow cleanup only in node_modules; ask on network calls like curl/wget; block kubectl delete or SQL DROP, each with a clear reason)
- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)
- Adopt lightweight governance that survives churn (MCP/skills/etc): just add columns/rules as new tools and metadata show up
- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why
Comments URL: https://news.ycombinator.com/item?id=46636786
Points: 5
# Comments: 1
Sign in to read the full article.
Sign in with Google