Grok SQLGuard — Execution Certificate Firewall Resource/Fail-closed write gate
How to: Grok SQLGuard — Execution Certificate Firewall Fail-closed write gate
Add SQLGuard — Execution Certificate Firewall to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"sqlguard": {
"type": "http",
"url": "https://sqlguard.io/mcp"
}
}
}-
02
Save the file and restart Grok.
-
03
Fail-closed write gate is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.
-
04
If it does not appear, check that SQLGuard — Execution Certificate Firewall is connected and that you are looking at its resources rather than its tools.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Same resource, other clients
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.