High Risk →

gog_auth_run

Run any gog auth subcommand. Run `gog auth --help` to see all available subcommands and flags. Note: for browser-based authorization, use gog_auth_add instead.

Part of the Gogcli MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

gogcli-mcp Execute

AI agents invoke gog_auth_run to trigger processes or run actions in Gogcli. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

gog_auth_run can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

gogcli.yaml
tools:
  gog_auth_run:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Gogcli policy for all 109 tools.

Tool Name gog_auth_run
Category Execute
MCP Server Gogcli MCP Server
Risk Level High

View all 109 tools →

Agents calling execute-class tools like gog_auth_run have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

gog_auth_run is one of the high-risk operations in Gogcli. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the gog_auth_run tool do? +

Run any gog auth subcommand. Run `gog auth --help` to see all available subcommands and flags. Note: for browser-based authorization, use gog_auth_add instead.. It is categorised as a Execute tool in the Gogcli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gog_auth_run? +

Add a rule in your Intercept YAML policy under the tools section for gog_auth_run. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Gogcli MCP server.

What risk level is gog_auth_run? +

gog_auth_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gog_auth_run? +

Yes. Add a rate_limit block to the gog_auth_run rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block gog_auth_run completely? +

Set action: deny in the Intercept policy for gog_auth_run. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides gog_auth_run? +

gog_auth_run is provided by the Gogcli MCP server (gogcli-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.