Developer builds open-source gateway to keep AI agents away from database credentials

·1 views

A developer created n0, an open-source Go platform designed to sit between AI agents and enterprise databases, after concluding that giving agents direct database access posed unacceptable security risks. Even read-only database credentials can enable harmful actions such as runaway queries, unauthorized table access, or excessive data exposure. The gateway handles authentication and tenant context via JWT middleware, while a separate query engine evaluates whether SQL is safe to execute before any request reaches the database. Agents interact only through a limited set of six tools — such as schema lookup and paginated result fetching — with no tool available to retrieve credentials or switch tenants. The project is described as working software rather than a complete production solution, with its architecture intended to enforce a clear separation between what an agent can request and what the platform permits it to do.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

One Question That Helps You Pick the Right Chart Every Time

A data visualization guide argues that chart selection should be driven by a single question: what comparison must the reader make? The framework maps four possible answers to four chart types — categories to bar charts, time to line charts, relationships to scatter plots, and part-of-whole also to bar charts. The guide warns that using the wrong chart type makes the intended comparison harder while inadvertently highlighting a different, misleading one. It also notes that pie charts are only suitable when showing parts of a whole with three or fewer slices. The practical advice is to open any existing chart, state aloud what comparison it is meant to show, and rebuild it if the chart type does not match that comparison.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Budget Variance Reports Mislead and How to Read Them Correctly

Budget vs actual variance analysis is a common financial tool, but it frequently misleads readers due to two key traps: the sign trap and the percentage trap. The variance formula — actual minus budget — produces a positive number whether revenue exceeds plan (good news) or costs exceed plan (bad news), meaning the sign alone cannot convey whether a result is favorable or unfavorable. To avoid misinterpretation, finance analysts label each variance line as F (favorable) or U (unfavorable) based on the line type, since over-budget revenue helps profit while over-budget costs hurt it. A worked example illustrates this with an eight-line department report, showing how the largest percentage variance and the largest dollar variance often belong to different rows, with the dollar figure typically deserving more attention. Understanding these conventions allows readers to interpret variance tables accurately and build reports that do not mislead others.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Operations Analytics Fundamentals: Key Metrics Every Analyst Must Know

A comprehensive guide published on DEV Community breaks down the core metrics used in operations analytics, including throughput, cycle time, backlog, utilization, and error rate. The piece explains how these numbers measure how work moves through any process, whether in a coffee shop, hospital ward, warehouse, or support inbox. A central concept illustrated is that work in progress and time in system are distinct but mathematically linked measures over the same workflow. The guide also warns readers not to confuse operations analytics with operations research, which is a separate, mathematics-heavy discipline focused on optimizing decisions. It is designed as a concept-layer reference for aspiring operations analysts preparing for technical screens or their first real dataset.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Chrome Extension to Schedule and Reopen Browser Tabs

A remote developer working from an RV created a Chrome extension called Tab Reminder after accidentally closing a tab with critical information and spending hours recovering it. The tool allows users to schedule browser tabs to reopen at a specified later time, preventing loss of important browsing sessions. It was built using the Chrome extension API, specifically the chrome.tabs.query method to retrieve and manage open tabs. The developer says the extension has helped free up mental energy by automating tab management, allowing focus on more complex work. Tab Reminder is available for download and is aimed at users who regularly manage large numbers of open browser tabs.

0 comments Read more at DEV Community