Tuning Engines - Governed AI Runtime runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 18 Aug 2026.
Govern model, agent, skill, and MCP workflows with policy, approvals, traces, and usage analytics.
What the code does
We read the source, 20 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.
const filePath = path.join(targetDir, name);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Alternatives to Tuning Engines - Governed AI Runtime
same job, measured the same wayCordon for MCP. Security gateway with policy enforcement, audit log, and HITL approvals.
Policy-based governance for AI agent tool calls. YAML policy, approval gates, audit logging.
Debug and analyze Nanostores apps with AI: scan stores, monitor runtime events, and search docs.
Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.
Security proxy that wraps MCP servers with real-time monitoring and policy enforcement
Security proxy that automatically wraps MCP servers with real-time monitoring and policy enforcement
MCP policy proxy: spend caps, approvals for destructive tools, kill switch, dry-run, audit log.
AI agent governance — security scanning, BYOK routing, audit logging, and Council approvals.
Tuning Engines - Governed AI Runtime — questions
Answers built from our own checks of this server.