<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tchesse Emmanuel</title>
    <description>The latest articles on DEV Community by Tchesse Emmanuel (@tchesse_emmanuel_3bcaf49e).</description>
    <link>https://dev.to/tchesse_emmanuel_3bcaf49e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4180434%2F11e9525d-0e29-4341-8bea-5b364755f103.png</url>
      <title>DEV Community: Tchesse Emmanuel</title>
      <link>https://dev.to/tchesse_emmanuel_3bcaf49e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tchesse_emmanuel_3bcaf49e"/>
    <language>en</language>
    <item>
      <title>I built an open-source "approval gate" for AI agents — here's why</title>
      <dc:creator>Tchesse Emmanuel</dc:creator>
      <pubDate>Tue, 13 Oct 2026 19:24:51 +0000</pubDate>
      <link>https://dev.to/tchesse_emmanuel_3bcaf49e/i-built-an-open-source-approval-gate-for-ai-agents-heres-why-58f3</link>
      <guid>https://dev.to/tchesse_emmanuel_3bcaf49e/i-built-an-open-source-approval-gate-for-ai-agents-heres-why-58f3</guid>
      <description>&lt;p&gt;AI agents are increasingly given real permissions — sending payments, &lt;br&gt;
emails, deleting files — often with little to no governance layer in &lt;br&gt;
between. I wanted a small, self-hosted tool that sits in front of any &lt;br&gt;
agent and decides whether a proposed action should go through, get &lt;br&gt;
blocked, or wait for a human to approve it.&lt;/p&gt;

&lt;p&gt;That's what InGravity is.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;Picture this: an AI agent in your n8n workflow proposes a $100,000 &lt;br&gt;
payment. Without anything in the way, the workflow might just submit &lt;br&gt;
it. Most "agent security" tools today either work at the network level &lt;br&gt;
(VPN tunneling, protocol parsing — powerful, but heavy to set up) or &lt;br&gt;
don't exist at all for smaller, workflow-level automations.&lt;/p&gt;

&lt;p&gt;I wanted something in between: simple enough to self-host in minutes, &lt;br&gt;
specific enough to actually stop a bad action before it happens.&lt;/p&gt;

&lt;h2&gt;
  
  
  What InGravity does
&lt;/h2&gt;

&lt;p&gt;InGravity evaluates an action against rules you configure, and returns &lt;br&gt;
a decision — before the action runs.&lt;/p&gt;

&lt;p&gt;Example:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;\&lt;/code&gt;&lt;code&gt;bash&lt;br&gt;
curl -X POST http://localhost:8080/check-action \&lt;br&gt;
  -H 'Content-Type: application/json' \&lt;br&gt;
  -d '{"action_type":"payment","amount":100000,"metadata":{"order_id":"order-123"}}'&lt;br&gt;
\&lt;/code&gt;&lt;code&gt;\&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Response: &lt;code&gt;blocked\&lt;/code&gt;, risk score &lt;code&gt;100\&lt;/code&gt;. The caller decides what to do &lt;br&gt;
next — InGravity doesn't execute, cancel, or intercept anything itself; &lt;br&gt;
it just gives you a clear, auditable answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's actually working today (being honest)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A rules engine + risk scoring API (&lt;code&gt;POST /check-action\&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;SQLite-backed history, persisted across restarts&lt;/li&gt;
&lt;li&gt;A dashboard to view past decisions and manually approve/block 
pending actions&lt;/li&gt;
&lt;li&gt;3 prebuilt rule templates (payments, emails, file access)&lt;/li&gt;
&lt;li&gt;A custom n8n node (&lt;code&gt;InGravity Guard\&lt;/code&gt;) that stops a workflow when 
an action is blocked&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What's NOT done yet
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No authentication on the API yet (don't expose it to untrusted 
networks — self-host only for now)&lt;/li&gt;
&lt;li&gt;No dry-run / simulation mode&lt;/li&gt;
&lt;li&gt;The n8n node is tested with simulated responses; real-workflow 
testing is in progress&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'd rather tell you this upfront than have you discover it the hard way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why open source
&lt;/h2&gt;

&lt;p&gt;I want to prove this is actually useful before thinking about anything &lt;br&gt;
commercial. If you're building with AI agents and this solves a real &lt;br&gt;
problem for you, I'd genuinely like to know — and if it doesn't, I'd &lt;br&gt;
like to know that too.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Tchesseludovic17-cloud/ingravity" rel="noopener noreferrer"&gt;https://github.com/Tchesseludovic17-cloud/ingravity&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>ai</category>
      <category>automation</category>
    </item>
    <item>
      <title>AI agents are getting real permissions — payments, emails, file access 
— often with no governance layer in between. I built InGravity to fix 
that: a small, self-hosted API that checks a proposed action against 
rules you configure, and returns a decision</title>
      <dc:creator>Tchesse Emmanuel</dc:creator>
      <pubDate>Tue, 13 Oct 2026 19:19:01 +0000</pubDate>
      <link>https://dev.to/tchesse_emmanuel_3bcaf49e/ai-agents-are-getting-real-permissions-payments-emails-file-access-often-with-no-governance-37c0</link>
      <guid>https://dev.to/tchesse_emmanuel_3bcaf49e/ai-agents-are-getting-real-permissions-payments-emails-file-access-often-with-no-governance-37c0</guid>
      <description></description>
    </item>
    <item>
      <title>AI agents are increasingly given real permissions — sending payments, 
emails, deleting files — often with little to no governance layer in 
between. I wanted a small, self-hosted tool that sits in front of any 
agent and decides whether a proposed action</title>
      <dc:creator>Tchesse Emmanuel</dc:creator>
      <pubDate>Tue, 13 Oct 2026 19:09:29 +0000</pubDate>
      <link>https://dev.to/tchesse_emmanuel_3bcaf49e/ai-agents-are-increasingly-given-real-permissions-sending-payments-emails-deleting-files--58g1</link>
      <guid>https://dev.to/tchesse_emmanuel_3bcaf49e/ai-agents-are-increasingly-given-real-permissions-sending-payments-emails-deleting-files--58g1</guid>
      <description></description>
    </item>
  </channel>
</rss>
