AISentinel by BizDNAi runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 10 Jul 2026.
Pre-tool policy enforcement + JSONL audit for AI agents. Apache 2.0.
We read the source, 17 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
logPath := filepath.Join(*logDir, "events-"+time.Now().UTC().Format("2006-01-02")+".jsonl")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Zero-trust gateway for AI agents: score tool calls, verify agent cards, enforce policy, audit.
Credential broker for AI agents: scoped, revocable API access with policy enforcement and audit.
Deterministic policy enforcement and MCP management for AI agent tool calls.
Non-custodial Kaspa policy enforcement for AI agents; signers retain custody.
Episodic memory, Frames, Policy Neighborhoods, and policy enforcement for AI agents.
Zero-trust MCP security proxy with policy enforcement, PII scrubbing, approvals, and audit trails.
Policy-based governance for AI agent tool calls. YAML policy, approval gates, audit logging.
Run MCP tool calls through Runestone Gatekeeper — policy enforcement, human approval, audit.
Answers built from our own checks of this server.