Skip to content
actionlake
Start free

Connectors · Identity & security

GitGuardian MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to GitGuardian and the rest of your systems. It gives your agent 198 GitGuardian actions (101 reads, 72 writes and 25 that wait for a confirmation) and holds the GitGuardian credential itself, so the agent never does. It paces GitGuardian's limits and records every call.

Connect GitGuardian freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "gitguardian.teams.list",  intent: "check which GitGuardian account is connected"}# List teams · read · 1 upstream call
  • 198actionsin one signed file
  • 101readlook, never change
  • 72writecreate and update
  • 25wait for a yesdestructive, confirmed first

Set up

Connect GitGuardian in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect GitGuardian.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyGitGuardian personal access token or service account token (Dashboard > API > Personal access tokens / Service…
    • hostWhere your GitGuardian lives: your host
    account { op: "connections.requirements", service: "gitguardian" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "gitguardian.teams.list" }# list teams · read · 1 upstream callcheck { action: "gitguardian.teams.delete", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

GitGuardian at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Setup fields
host
Limits we pace to
15 calls a second, per connection
API covered
GitGuardian API v1 (OpenAPI 3.0.3, 1.1.0), at your GitGuardian instance's API base URL, which you enter when connecting
Built from
GitGuardian's documentation, read 23 October 2026api.gitguardian.comapi.gitguardian.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
55 of 101 reads, for up to 5 minutes; a write clears what it affects
Shared entities
3, so ask can line GitGuardian up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in GitGuardian.

198 actions in 39 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 101readlook, never change
  • 72writecreate and update
  • 25destructivewait for a confirmation

  1. Secret incidents

    29

    14 read · 12 write · 3 destructive

    List secret incidents · List notes on a secret incident · Create a secret incident note · Retrieve a secret incident

  2. Teams

    24

    9 read · 10 write · 5 destructive

    List teams · Create a team · Retrieve a team · Update a team

  3. Public secret incidents

    20

    7 read · 12 write · 1 destructive

    Create a public secret incident note · List public secret incidents · List activity logs of a public secret incident · List notes on a public secret incident

  4. Honeytokens

    14

    6 read · 6 write · 2 destructive

    Bulk prefix lookup for honeytoken HMSL hashes · Create a honeytoken · Create an honeytoken note · Create a honeytoken within a context

  5. Members

    13

    8 read · 3 write · 2 destructive

    List members · Update a member · Retrieve a member · List secret incidents a member has access to

  6. Invitations

    9

    4 read · 3 write · 2 destructive

    List invitations · Create an invitation · Delete an invitation · Retrieve an invitation

  7. Custom tags

    8

    2 read · 4 write · 2 destructive

    Create a custom tag · List custom tags · Retrieve a custom tag · Partial update of a Custom Tag

  8. Nhi identities

    7

    4 read · 2 write · 1 destructive

    Add owners to an identity · List identities · List the locations of an identity · Retrieve an identity

31 more areas · 74 actions
  • API tokens 6
  • Scim groups 6
  • Scim users 6
  • Sources 6
  • Custom sources 5
  • Ip allowlist 5
  • Secrets 4
  • Health checks 3
  • Honeytoken endpoint deployments 3
  • Scan 3
  • Audit logs 2
  • Check runs 2
  • Scans 2
  • Scim resource types 2
  • Scim schemas 2
  • Secret detectors 2
  • Code fix requests 1
  • Detector custom hosts 1
  • Developers 1
  • Health 1
  • Honeytoken events 1
  • Ip addresses 1
  • JWKS 1
  • Nhi sources 1
  • Oauth server metadata 1
  • Oidc configuration 1
  • Quotas 1
  • Remediation workflow 1
  • Scim service provider config 1
  • Secret occurrences 1
  • Severity rules 1

Top actions

The GitGuardian API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 35 of GitGuardian's 35 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
gitguardian.teams.listList teamsList teams.readidentity.group.list262 connectors
gitguardian.scim_groups.listList groups (SCIM)List groups (SCIM).readidentity.group.list262 connectors
gitguardian.scim_users.listList members (SCIM)List members (SCIM).readidentity.user.list474 connectors
gitguardian.teams.deleteDelete a teamDelete a team.destructiveidentity.group.delete181 connectors
gitguardian.scim_users.createCreate a member (SCIM)Create a member (SCIM).writeidentity.user.create262 connectors
gitguardian.sources.listList sourcesList sources.readdevops.repository.list28 connectors
gitguardian.members.listList membersList members.readwork.workspace_member.list26 connectors
gitguardian.api_tokens.createCreate an API token.Create an API token.writeidentity.api_key.create100 connectors
gitguardian.api_tokens.listList API tokens.List API tokens.readidentity.api_key.list96 connectors
gitguardian.audit_logs.listList audit LogsList audit Logs.readsecurity.audit_log.list69 connectors
gitguardian.sources.getRetrieve a sourceRetrieve a source.readdevops.repository.get26 connectors
gitguardian.members.updateUpdate a memberUpdate a member.writework.workspace_member.update16 connectors

Try it

Prompts to paste into Claude.

Each one names the GitGuardian actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    List our GitGuardian repositories with their visibility and default branch.

    callsgitguardian.sources.list

  2. Writewrite

    Create a member (SCIM) in GitGuardian. Show me exactly what you will send before you save it.

    callsgitguardian.scim_users.create

Governance for GitGuardian

Destructive actions wait for a yes.

25 GitGuardian actions are destructive. These are all of them:

  • Delete a teamgitguardian.teams.delete
  • Delete a member (SCIM)gitguardian.scim_users.delete
  • Revoke an API token.gitguardian.api_tokens.delete
  • Delete a secret incident notegitguardian.secret_incidents.delete_note
  • Delete an invitationgitguardian.invitations.delete
  • Delete a membergitguardian.members.delete
  • Deletion of a custom taggitguardian.custom_tags.delete
  • Revoke the honeytokengitguardian.honeytokens.revoke
  • Delete a group (SCIM)gitguardian.scim_groups.delete
  • Delete an IP allowlist rulegitguardian.ip_allowlist.delete
  • Cancel or decline a team requestgitguardian.teams.delete_request
  • Delete a custom sourcegitguardian.custom_sources.delete
  • Revoke the current API token.gitguardian.api_tokens.delete_self
  • Delete a custom tags keygitguardian.custom_tags.delete_key
  • Delete a honeytoken notegitguardian.honeytokens.delete_note
  • Delete a team invitationgitguardian.teams.delete_invitation
  • Remove a member from a teamgitguardian.teams.delete_membership
  • Remove an owner from an identitygitguardian.nhi_identities.remove_owner
  • Revoke a team's access to a resourcegitguardian.teams.revoke_resource_access
  • Revoke a member's access to a resourcegitguardian.members.revoke_resource_access
  • Revoke access to a secret incidentgitguardian.secret_incidents.revoke_access
  • Remove the validity override of a secretgitguardian.secrets.remove_validity_override
  • Revoke an invitation's access to a resourcegitguardian.invitations.revoke_resource_access
  • Delete a public secret incident notegitguardian.public_secret_incidents.delete_note
  • Unlink a ticket from a secret incident, public incident or honeytokengitguardian.secret_incidents.unlink_destination_ticket

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dogitguardian.teams.deleteconfirm_policy: human

Delete a team?

intent: the user asked me to delete a team

run suspended · waiting for a named person · key gitguardian-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "gitguardian-agent",  allowed_actions: ["gitguardian.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "gitguardian.teams.delete", approver: "[email protected]" },    { match: "gitguardian.scim_users.delete", approver: "[email protected]" },    { match: "gitguardian.api_tokens.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to GitGuardian only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What GitGuardian costs on actionlake.

Every GitGuardian action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call GitGuardian refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 198 GitGuardian actions
  • 198actions pageeach page of a long list is one call
  • 55reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every GitGuardian action.

198 actions by area: the id your agent calls, what it does, and its effect.

Secret incidents29
  • gitguardian.secret_incidents.assignAssign a secret incidentwrite
  • gitguardian.secret_incidents.check_presenceRequest a new presence check for a secret incidentwrite
  • gitguardian.secret_incidents.create_noteCreate a secret incident notewrite
  • gitguardian.secret_incidents.delete_noteDelete a secret incident notedestructive
  • gitguardian.secret_incidents.getRetrieve a secret incidentread
  • gitguardian.secret_incidents.get_impacted_perimeterRetrieve the impacted perimeter of a secret incidentread
  • gitguardian.secret_incidents.grant_accessGrant access to a secret incidentwrite
  • gitguardian.secret_incidents.ignoreIgnore a secret incidentwrite
  • gitguardian.secret_incidents.listList secret incidentsread
  • gitguardian.secret_incidents.list_activity_logsList activity logs of a secret incidentread
  • gitguardian.secret_incidents.list_invitation_accessList invitations with access to a secret incidentread
  • gitguardian.secret_incidents.list_invitationsList invitations having access to a Secret Incidentread
  • gitguardian.secret_incidents.list_leaksRetrieve where a secret has been publicly leakedread
  • gitguardian.secret_incidents.list_locationsList locations of a secret incidentread
  • gitguardian.secret_incidents.list_member_accessList members with access to a secret incidentread
  • gitguardian.secret_incidents.list_membersList members having access to a secret incidentread
  • gitguardian.secret_incidents.list_notesList notes on a secret incidentread
  • gitguardian.secret_incidents.list_team_accessList teams with access to a secret incidentread
  • gitguardian.secret_incidents.list_teamsList teams having access to a secret incidentread
  • gitguardian.secret_incidents.list_vaultsGet vault information for a secret incidentread
  • gitguardian.secret_incidents.reopenReopen a secret incidentwrite
  • gitguardian.secret_incidents.resolveResolve a secret incidentwrite
  • gitguardian.secret_incidents.revoke_accessRevoke access to a secret incidentdestructive
  • gitguardian.secret_incidents.shareShare a secret incidentwrite
  • gitguardian.secret_incidents.unassignUnassign a secret incidentwrite
  • gitguardian.secret_incidents.unlink_destination_ticketUnlink a ticket from a secret incident, public incident or honeytokendestructive
  • gitguardian.secret_incidents.unshareUnshare a secret incidentwrite
  • gitguardian.secret_incidents.updateUpdate a secret incidentwrite
  • gitguardian.secret_incidents.update_noteUpdate a secret incident notewrite
Teams24
  • gitguardian.teams.accept_requestAccept a team requestwrite
  • gitguardian.teams.createCreate a teamwrite
  • gitguardian.teams.create_invitationCreate a team invitationwrite
  • gitguardian.teams.create_membershipAdd a member to a teamwrite
  • gitguardian.teams.create_requestRequest access to a teamwrite
  • gitguardian.teams.deleteDelete a teamdestructive
  • gitguardian.teams.delete_invitationDelete a team invitationdestructive
  • gitguardian.teams.delete_membershipRemove a member from a teamdestructive
  • gitguardian.teams.delete_requestCancel or decline a team requestdestructive
  • gitguardian.teams.getRetrieve a teamread
  • gitguardian.teams.get_resource_accessCheck team permission for a resourceread
  • gitguardian.teams.listList teamsread
  • gitguardian.teams.list_invitationsList team invitationsread
  • gitguardian.teams.list_membershipsList team membershipsread
  • gitguardian.teams.list_requestsList team requests of a teamread
  • gitguardian.teams.list_secret_incident_accessList secret incidents a team has access toread
  • gitguardian.teams.list_secret_incidentsList secret incidents of a teamread
  • gitguardian.teams.list_sourcesList team sourcesread
  • gitguardian.teams.revoke_resource_accessRevoke a team's access to a resourcedestructive
  • gitguardian.teams.set_resource_accessGive a team access to a resourcewrite
  • gitguardian.teams.updateUpdate a teamwrite
  • gitguardian.teams.update_invitationUpdate a team invitationwrite
  • gitguardian.teams.update_membershipUpdate a team membershipwrite
  • gitguardian.teams.update_sourcesUpdate a team perimeterwrite
Public secret incidents20
  • gitguardian.public_secret_incidents.assignAssign a public secret incidentwrite
  • gitguardian.public_secret_incidents.check_presenceRequest a new presence check for a public secret incidentwrite
  • gitguardian.public_secret_incidents.create_noteCreate a public secret incident notewrite
  • gitguardian.public_secret_incidents.delete_noteDelete a public secret incident notedestructive
  • gitguardian.public_secret_incidents.getRetrieve a public secret incidentread
  • gitguardian.public_secret_incidents.get_occurrenceRetrieve a public secret occurrenceread
  • gitguardian.public_secret_incidents.ignoreIgnore a public secret incidentwrite
  • gitguardian.public_secret_incidents.listList public secret incidentsread
  • gitguardian.public_secret_incidents.list_activity_logsList activity logs of a public secret incidentread
  • gitguardian.public_secret_incidents.list_notesList notes on a public secret incidentread
  • gitguardian.public_secret_incidents.list_occurrencesList public secret occurrencesread
  • gitguardian.public_secret_incidents.list_vaultsGet vault information for a public secret incidentread
  • gitguardian.public_secret_incidents.reopenReopen a public secret incidentwrite
  • gitguardian.public_secret_incidents.resolveResolve a public secret incidentwrite
  • gitguardian.public_secret_incidents.set_custom_tagsSet custom tags of a public secret incidentwrite
  • gitguardian.public_secret_incidents.set_severitySet severity of a public secret incidentwrite
  • gitguardian.public_secret_incidents.shareShare a public secret incidentwrite
  • gitguardian.public_secret_incidents.unassignUnassign a public secret incidentwrite
  • gitguardian.public_secret_incidents.unshareUnshare a public secret incidentwrite
  • gitguardian.public_secret_incidents.update_noteUpdate a public secret incident notewrite
Honeytokens14
  • gitguardian.honeytokens.check_prefixesBulk prefix lookup for honeytoken HMSL hashesread
  • gitguardian.honeytokens.createCreate a honeytokenwrite
  • gitguardian.honeytokens.create_noteCreate an honeytoken notewrite
  • gitguardian.honeytokens.create_with_contextCreate a honeytoken within a contextwrite
  • gitguardian.honeytokens.delete_noteDelete a honeytoken notedestructive
  • gitguardian.honeytokens.getRetrieve a honeytokenread
  • gitguardian.honeytokens.listList honeytokensread
  • gitguardian.honeytokens.list_activity_logsList activity logs of a honeytokenread
  • gitguardian.honeytokens.list_notesList notes on an honeytokenread
  • gitguardian.honeytokens.list_sourcesList sources on an honeytokenread
  • gitguardian.honeytokens.resetReset the honeytokenwrite
  • gitguardian.honeytokens.revokeRevoke the honeytokendestructive
  • gitguardian.honeytokens.updateUpdate a honeytokenwrite
  • gitguardian.honeytokens.update_noteUpdate a honeytoken notewrite
Members13
  • gitguardian.members.deleteDelete a memberdestructive
  • gitguardian.members.getRetrieve a memberread
  • gitguardian.members.get_email_notificationsRetrieve a member's email settingsread
  • gitguardian.members.get_resource_accessCheck member permission for a resourceread
  • gitguardian.members.listList membersread
  • gitguardian.members.list_secret_incident_accessList secret incidents a member has access toread
  • gitguardian.members.list_team_membershipsList team memberships of a memberread
  • gitguardian.members.list_team_requestsList team requests of a memberread
  • gitguardian.members.list_teamsList teams of a memberread
  • gitguardian.members.revoke_resource_accessRevoke a member's access to a resourcedestructive
  • gitguardian.members.set_resource_accessGive a member access to a resourcewrite
  • gitguardian.members.updateUpdate a memberwrite
  • gitguardian.members.update_email_notificationsUpdate a member's email settingswrite
Invitations9
  • gitguardian.invitations.createCreate an invitationwrite
  • gitguardian.invitations.deleteDelete an invitationdestructive
  • gitguardian.invitations.getRetrieve an invitationread
  • gitguardian.invitations.get_resource_accessCheck invitation permission for a resourceread
  • gitguardian.invitations.listList invitationsread
  • gitguardian.invitations.list_secret_incident_accessList secret incidents an invitation has access toread
  • gitguardian.invitations.resendResend an invitationwrite
  • gitguardian.invitations.revoke_resource_accessRevoke an invitation's access to a resourcedestructive
  • gitguardian.invitations.set_resource_accessGive an invitation access to a resourcewrite
Custom tags8
  • gitguardian.custom_tags.createCreate a custom tagwrite
  • gitguardian.custom_tags.deleteDeletion of a custom tagdestructive
  • gitguardian.custom_tags.delete_keyDelete a custom tags keydestructive
  • gitguardian.custom_tags.getRetrieve a custom tagread
  • gitguardian.custom_tags.listList custom tagsread
  • gitguardian.custom_tags.patchPartial update of a Custom Tagwrite
  • gitguardian.custom_tags.rename_keyUpdate custom tags keywrite
  • gitguardian.custom_tags.updateFull Update of a Custom Tagwrite
Nhi identities7
  • gitguardian.nhi_identities.add_ownersAdd owners to an identitywrite
  • gitguardian.nhi_identities.getRetrieve an identityread
  • gitguardian.nhi_identities.listList identitiesread
  • gitguardian.nhi_identities.list_locationsList the locations of an identityread
  • gitguardian.nhi_identities.list_ownersList owners of an identityread
  • gitguardian.nhi_identities.remove_ownerRemove an owner from an identitydestructive
  • gitguardian.nhi_identities.replace_ownersReplace the owners of an identitywrite
API tokens6
  • gitguardian.api_tokens.createCreate an API token.write
  • gitguardian.api_tokens.deleteRevoke an API token.destructive
  • gitguardian.api_tokens.delete_selfRevoke the current API token.destructive
  • gitguardian.api_tokens.getRetrieve details of an API token.read
  • gitguardian.api_tokens.get_selfRetrieve details of the current API token.read
  • gitguardian.api_tokens.listList API tokens.read
Scim groups6
  • gitguardian.scim_groups.createCreate a group (SCIM)write
  • gitguardian.scim_groups.deleteDelete a group (SCIM)destructive
  • gitguardian.scim_groups.getDetail of a group (SCIM)read
  • gitguardian.scim_groups.listList groups (SCIM)read
  • gitguardian.scim_groups.patchPartially update a group (SCIM)write
  • gitguardian.scim_groups.replaceUpdate a group (SCIM)write
Scim users6
  • gitguardian.scim_users.createCreate a member (SCIM)write
  • gitguardian.scim_users.deleteDelete a member (SCIM)destructive
  • gitguardian.scim_users.getDetail of a member (SCIM)read
  • gitguardian.scim_users.listList members (SCIM)read
  • gitguardian.scim_users.patchUpdate (partial) of a member (SCIM)write
  • gitguardian.scim_users.replaceUpdate of a member (SCIM)write
Sources6
  • gitguardian.sources.getRetrieve a sourceread
  • gitguardian.sources.listList sourcesread
  • gitguardian.sources.list_locationsList locations of a sourceread
  • gitguardian.sources.list_secret_incidentsList secret incidents of a sourceread
  • gitguardian.sources.trigger_scansTrigger scans on sourceswrite
  • gitguardian.sources.updateUpdate a sourcewrite
Custom sources5
  • gitguardian.custom_sources.createCreate custom sourcewrite
  • gitguardian.custom_sources.deleteDelete a custom sourcedestructive
  • gitguardian.custom_sources.getGet a custom sourceread
  • gitguardian.custom_sources.listList custom sourcesread
  • gitguardian.custom_sources.updateUpdate a custom sourcewrite
Ip allowlist5
  • gitguardian.ip_allowlist.createCreate an IP allowlist rulewrite
  • gitguardian.ip_allowlist.deleteDelete an IP allowlist ruledestructive
  • gitguardian.ip_allowlist.getRetrieve an IP allowlist ruleread
  • gitguardian.ip_allowlist.listList IP allowlist rulesread
  • gitguardian.ip_allowlist.updateUpdate an IP allowlist rulewrite
Secrets4
  • gitguardian.secrets.getRetrieve a secret valueread
  • gitguardian.secrets.get_validityGet the validity of a secretread
  • gitguardian.secrets.remove_validity_overrideRemove the validity override of a secretdestructive
  • gitguardian.secrets.set_validity_overrideOverride the validity of a secretwrite
Health checks3
  • gitguardian.health_checks.listList health checksread
  • gitguardian.health_checks.list_instance_historyList health check history for an instanceread
  • gitguardian.health_checks.triggerTrigger a health checkwrite
Honeytoken endpoint deployments3
  • gitguardian.honeytoken_endpoint_deployments.confirmConfirm a honeytoken endpoint deploymentwrite
  • gitguardian.honeytoken_endpoint_deployments.createReconcile (plant) honeytokens for a machine/userwrite
  • gitguardian.honeytoken_endpoint_deployments.listList a machine/user's honeytoken deployments (read-only)read
Scan3
  • gitguardian.scan.contentContent scanread
  • gitguardian.scan.create_incidentsScan content and create incidentswrite
  • gitguardian.scan.multipleMultiple content scanread
Audit logs2
  • gitguardian.audit_logs.listList audit Logsread
  • gitguardian.audit_logs.list_event_namesList audit log event namesread
Check runs2
  • gitguardian.check_runs.listList GitHub check runsread
  • gitguardian.check_runs.skipSkip a GitHub check runwrite
Scans2
  • gitguardian.scans.getRetrieve a scanread
  • gitguardian.scans.listList scansread
Scim resource types2
  • gitguardian.scim_resource_types.getResource Types (SCIM)read
  • gitguardian.scim_resource_types.listList Resource Types (SCIM)read
Scim schemas2
  • gitguardian.scim_schemas.getSchema (SCIM)read
  • gitguardian.scim_schemas.listList Schemas (SCIM)read
Secret detectors2
  • gitguardian.secret_detectors.getGet a secret detectorread
  • gitguardian.secret_detectors.listList secret detectorsread
Code fix requests1
  • gitguardian.code_fix_requests.createCreate code fix requestswrite
Detector custom hosts1
  • gitguardian.detector_custom_hosts.listList detector custom hostsread
Developers1
  • gitguardian.developers.listList developersread
Health1
  • gitguardian.health.getAPI Healthread
Honeytoken events1
  • gitguardian.honeytoken_events.listList all honeytokens eventsread
Ip addresses1
  • gitguardian.ip_addresses.getList GitGuardian IP addressesread
JWKS1
  • gitguardian.jwks.getList public keys used to sign JWTs.read
Nhi sources1
  • gitguardian.nhi_sources.listList sourcesread
Oauth server metadata1
  • gitguardian.oauth_server_metadata.getOAuth 2.0 Authorization Server Metadata.read
Oidc configuration1
  • gitguardian.oidc_configuration.getOpenID Connect discovery document.read
Quotas1
  • gitguardian.quotas.getQuota overviewread
Remediation workflow1
  • gitguardian.remediation_workflow.getRetrieve the remediation workflowread
Scim service provider config1
  • gitguardian.scim_service_provider_config.getService Provider Configuration (SCIM)read
Secret occurrences1
  • gitguardian.secret_occurrences.listList secret occurrencesread
Severity rules1
  • gitguardian.severity_rules.listList severity rulesread

Questions

The GitGuardian MCP server, answered.

Is there a GitGuardian MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 198 GitGuardian actions across secret incidents, teams, public secret incidents and honeytokens, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by GitGuardian.

What do I need to connect GitGuardian?

GitGuardian personal access token or service account token (Dashboard > API > Personal access tokens / Service…. Plus your host. The free call account { op: "connections.requirements", service: "gitguardian" } lists exactly what to paste.

Can an AI agent delete or change things in GitGuardian?

Only if its key allows it, and only with an explicit confirmation. 25 GitGuardian actions are destructive, including delete a team, delete a member (SCIM) and revoke an API token.. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my GitGuardian API limit?

actionlake paces every call to the limits in the GitGuardian service file: 15 calls a second per connection. Repeated reads are answered from cache (55 GitGuardian actions can be), which never reaches GitGuardian.

What does a GitGuardian action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (198 GitGuardian actions page). Cache hits, searches, dry runs and calls GitGuardian refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which GitGuardian API does it cover?

The GitGuardian API v1 (OpenAPI 3.0.3, 1.1.0) at your GitGuardian instance's API base URL, which you enter when connecting. It is built from GitGuardian's documentation as read on 23 October 2026. 198 actions in 39 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my GitGuardian data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your GitGuardian credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like GitGuardian

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by GitGuardian; the name is the vendor's own. Counts are from the GitGuardian service file, version 1.0.0.

Give your agent GitGuardian today.

Connect GitGuardian freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.