From ff242b5eca04e1d90331e32f611d7dcaf91c3de5 Mon Sep 17 00:00:00 2001
From: armorer-labs <armorer-labs@users.noreply.github.com>
Date: Tue, 19 May 2026 11:34:46 +0800
Subject: [PATCH] Document Armorer Guard MCP proxy

---
 MCP_SETUP.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/MCP_SETUP.md b/MCP_SETUP.md
index 2d82e6b2..af67a311 100644
--- a/MCP_SETUP.md
+++ b/MCP_SETUP.md
@@ -55,6 +55,30 @@ Add this JSON configuration to your Dive MCP settings to enable local tools:
   }
 ```
 
+To gate local MCP tool calls before they reach a server, wrap the server command
+with [Armorer Guard](https://github.com/ArmorerLabs/Armorer-Guard). For example:
+
+```json
+ "mcpServers":{
+    "filesystem": {
+      "command": "armorer-guard",
+      "args": [
+        "mcp-proxy",
+        "--",
+        "npx",
+        "-y",
+        "@modelcontextprotocol/server-filesystem",
+        "/path/to/allowed/files"
+      ],
+      "enabled": true
+    }
+  }
+```
+
+Armorer Guard runs locally and inspects STDIO MCP `tools/call` arguments for
+prompt injection, credential leakage, exfiltration risk, and dangerous actions
+before forwarding safe calls.
+
 #### Using Streamable HTTP for Cloud MCP Services
 
 You can connect to external cloud MCP servers via Streamable HTTP transport. Here's the Dive configuration example for SearXNG service from OAPHub: