From 3e7d4bfa0ed1b3a6577d1cc5632150d805650a47 Mon Sep 17 00:00:00 2001
From: knielsen404 <kristian@invariantlabs.ai>
Date: Mon, 26 May 2025 14:56:23 +0100
Subject: [PATCH] add custom guardrails sectios to client level

---
 docs/mcp-scan/guardrails.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/mcp-scan/guardrails.md b/docs/mcp-scan/guardrails.md
index e9ae49d..c4307ec 100644
--- a/docs/mcp-scan/guardrails.md
+++ b/docs/mcp-scan/guardrails.md
@@ -42,12 +42,15 @@ The configuration file defines guardrailing behavior hierarchically, scoped by *
 
 ```yaml
 <client-name>:
+  custom_guardrails:
+    ...
+
   <server-name>:
     guardrails:
       <default-guardrail-name>: <guardrail-action>
         ...
 
-      custom_guardrails:
+      custom_guardrails: 
         - name: <guardrail-name>
           id: <guardrail-id>
           action: <guardrail-action>
@@ -107,6 +110,9 @@ Custom guardrails allow you to define rules tailored to specific workflows, data
 
 To get started writing custom rules, refer to the [rule writing reference](./rules.md) to get started quickly with writing guardrails, or explore the rest of this documentation to learn about the concepts in depth, perhaps [starting with this introduction](./index.md).
 
+!!! note
+    You can add `custom_guardrails` on either a per-client or a per-server level. If you add it at the client level, the guardrail will be enforced on all servers used by that client.
+
 ### Schema
 A custom guardrail is defined using the following fields: