Cline Sunaiva Gate — Agent Rule Enforcement delete_custom_rule
How to: Cline Sunaiva Gate — Agent Rule Enforcement delete_custom_rule
Add Sunaiva Gate — Agent Rule Enforcement to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"gate": {
"url": "https://mcp.sunaivacore.io"
}
}
}-
02
Save the file and restart Cline.
-
03
Ask for something delete_custom_rule does. Cline lists the server's tools on connect and calls delete_custom_rule itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Sunaiva Gate — Agent Rule Enforcement's identifier in your config matches the one above exactly.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Set these first
Sunaiva Gate — Agent Rule Enforcement will not start until these are set, so delete_custom_rule never becomes available.
-
SUNAIVA_GATE_API_KEY -
SUNAIVA_GATE_DRY_RUN -
DISABLE_SUNAIVA_GATE
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.