What can you do with the GitGuardian integration?

LiveContext exposes 17 operations on GitGuardian, covering incident, honeytoken, scan and detector. Common uses include access audit, coverage audit and commit scanning.

LiveContext

All integrations

GitGuardian integration

GitGuardian API for secret detection and remediation in code repositories. Scan code for exposed API keys, passwords, certificates, and other credentials. Monitor repositories in real-time, receive instant alerts on secret leaks, and track remediation progress. Essential for preventing credential exposure and maintaining security compliance in software development.

17 toolsAPI keyAPI docs

Connect GitGuardian How integrations work

Common GitGuardian use cases

access audit
coverage audit
commit scanning
incident triage
usage monitoring
security dashboard
intrusion detection
severity adjustment
honeytoken inventory
coverage documentation

What you can do with GitGuardian

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Incident, 8 operations

POSTassign_incident
Assigns a GitGuardian secret incident to a team member by email or member ID for investigation.
GETget_incident
Retrieves detailed information about a GitGuardian secret incident. Returns full context including occurrences, credential validity, feedback history, and remediation status.
POSTignore_incident
Ignores a GitGuardian secret incident with a documented reason: test_credential, false_positive, or low_risk.
GETlist_incidents
Lists secret incidents detected by GitGuardian. Returns exposed credentials with location, detector type, validity status, and remediation progress for security management.
POSTreopen_incident
Reopens a previously resolved or ignored GitGuardian secret incident, setting its status back to TRIGGERED.
POSTresolve_incident
Resolves a GitGuardian secret incident and optionally marks the credential as revoked/rotated.
POSTshare_incident
Creates a shareable link for a GitGuardian incident to share with developers for collaboration on remediation.
PATCHupdate_incident
Updates a GitGuardian secret incident properties like severity and custom tags. For status changes, use dedicated resolve/ignore/assign endpoints.

Honeytoken, 2 operations

POSTcreate_honeytoken
Creates a GitGuardian AWS honeytoken for intrusion detection. Generates fake AWS credentials that alert when used, detecting unauthorized access or data exfiltration.
GETlist_honeytokens
Lists all GitGuardian honeytokens in the workspace with their status, trigger history, and configuration details.

Scan, 2 operations

POSTmulti_scan_content
Batch scans multiple documents for secrets in a single GitGuardian API call. Efficient for scanning multiple files while consuming only 1 quota.
POSTscan_content
Scans text content for exposed secrets using GitGuardian. Detects 350+ types of credentials including API keys, passwords, private keys, and tokens with high accuracy.

Detector, 1 operation

GETlist_detectors
Lists GitGuardian secret detectors. Returns all credential types that can be detected including cloud keys, API tokens, private keys, and generic secrets.

Health, 1 operation

GETget_health
Checks GitGuardian API health and validates the API token. Returns status to verify connectivity and authentication.

Member, 1 operation

GETlist_members
Lists GitGuardian workspace members. Returns team members with access levels, activity info, and active status for access management.

Quota, 1 operation

GETget_quota
Retrieves GitGuardian API quota and usage information. Returns scan limits, remaining quota, and usage for the current period.

Source, 1 operation

GETlist_sources
Lists sources monitored by GitGuardian. Returns repositories and integrations being scanned with their health status, criticality, and incident counts.

Use GitGuardian from Claude Code, Cursor or Codex

Connect GitGuardian in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its GitGuardian operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect GitGuardian

Create your workspace
Sign up free. Nothing to install.
Connect GitGuardian once
Add your GitGuardian connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

GitGuardian integration FAQ

What can you do with the GitGuardian integration?: LiveContext exposes 17 operations on GitGuardian, covering incident, honeytoken, scan and detector. Common uses include access audit, coverage audit and commit scanning.