Skip to content

Commit 813a5aa

Browse files
Update README.md
1 parent 0135768 commit 813a5aa

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Using `mcp-scan proxy`, you can monitor, log, and safeguard all MCP traffic on y
6767

6868
#### Enforcing Guardrails
6969

70-
You can also add guardrailing rules, to restrict and validate the sequence of tool uses.
70+
You can also add guardrailing rules, to restrict and validate the sequence of tool uses passing through proxy.
7171

7272
For this, create a `~/.mcp-scan/guardrails_config.yml` with the following contents:
7373

@@ -78,7 +78,6 @@ For this, create a `~/.mcp-scan/guardrails_config.yml` with the following conten
7878
secrets: block # block calls/results with secrets
7979

8080
custom_guardrails:
81-
# define a rule using Invariant Guardrails, https://explorer.invariantlabs.ai/docs/guardrails/
8281
- name: "Filter tool results with 'error'"
8382
id: "error_filter_guardrail"
8483
action: block # or 'log'
@@ -89,6 +88,8 @@ For this, create a `~/.mcp-scan/guardrails_config.yml` with the following conten
8988
```
9089
From then on, all calls proxied via `mcp-scan proxy` will be checked against your configured guardrailing rules for the current client/server.
9190

91+
Custom guardrails are implemented using Invariant Guardrails. To learn more about these rules, [see this playground environment](https://explorer.invariantlabs.ai/docs/guardrails/) and the [official documentation](https://explorer.invariantlabs.ai/docs/).
92+
9293
## How It Works
9394

9495
### Scanning

0 commit comments

Comments
 (0)