- ACTIVE
- OWNED
- FIXED
- HUMAN
Short answer
How can I triage GitGuardian leaks using AI?
Your agent pulls active leaks from GitGuardian and lets you assign them to team members or mark them as resolved. You get a direct line of sight into every credential exposure without switching tabs.
Incident outcomes
Where every issue lands.
The agent organizes your security response into four clear states.
ACTIVE
Unassigned leaks
The agent identifies new exposures that need immediate attention. You see exactly what was leaked and where it happened.
OWNED
Assigned incidents
Once you pick a responder, the agent updates the incident status. This keeps your security workflow organized and accountable.
FIXED
Resolved secrets
After the credential is rotated or revoked, the agent closes the loop. This clears the incident from your active queue.
HUMAN
Manual review
Some leaks require deep investigation or manual rotation. The agent flags these for you to handle in the GitGuardian dashboard.
The workflow
What your AI does when a leak is detected.
The agent handles the heavy lifting of data retrieval and status updates.
Fetch leaks
The agent pulls a list of all current secret exposures from your account.
list_secret_incidentsInspect details
You can look at the specific metadata and context of a single leaked credential.
get_secret_incidentAssign owners
The agent links a specific incident to a person to ensure it gets handled.
assign_secret_incidentClose incidents
Once the threat is neutralized, the agent marks the incident as finished.
resolve_secret_incident
Try it
Copy these to start.
Use these prompts to kick off your triage process.
Starting points
Swap out the repo names or incident IDs with your actual GitGuardian data.
GitGuardian Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_NQtV8WXJZTZDwZLKUu4JIzBlR9PvO6RL6VjurLD6/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — GitGuardian capabilities are ready to use.
{
"mcpServers": {
"gitguardian-mcp": {
"url": "https://edge.vinkius.com/vk_preview_NQtV8WXJZTZDwZLKUu4JIzBlR9PvO6RL6VjurLD6/mcp"
}
}
}List all recent secret incidents in my GitGuardian account.
Get the details for incident ID 12345.
Assign incident 67890 to the security lead.
Mark the incident in the production repo as resolved.
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect GitGuardian once, then ask.
One connection gives your agent access to your GitGuardian data. Your credentials stay encrypted and secure.
Connect GitGuardian to your AIFAQ
How the triage process works
- 01
Can the AI delete a secret incident?
No. The agent can only resolve or update incidents using the available tools.
- 02
Can my AI rotate the actual API keys?
No. The agent manages the incident status in GitGuardian, but you must perform the actual credential rotation in your cloud provider or service.
- 03
Does the agent see all my code?
No. The agent only accesses the specific incident data provided by GitGuardian.
- 04
Can I update the notes on an incident?
Yes. You can use the agent to update incident details as you investigate.
- 05
How does the agent know which incidents are new?
The agent uses the list tool to pull current data and compares it to what you've already discussed.
More questions about GitGuardian? The Connector page answers them. See everything the GitGuardian Connector can do
Connect GitGuardian to Claude, Cursor, ChatGPT & more
