Skip to content

Gemini CLI IntentFence Agent Action Firewall intentfence_authorize_action

How to: Gemini CLI IntentFence Agent Action Firewall intentfence_authorize_action

client:Gemini CLI transport:streamable-http tool:intentfence_authorize_action

Add IntentFence Agent Action Firewall to Gemini CLI

  1. 01

    Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "intentfence": {
      "httpUrl": "https://agentpass-protocol.rmalka06.chatgpt.site/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something intentfence_authorize_action does. Gemini CLI lists the server's tools on connect and calls intentfence_authorize_action itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that IntentFence Agent Action Firewall's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

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.