--- title: "GitGuardian MCP server for AI agents - actionlake" description: "Give Claude 198 GitGuardian actions through one MCP server: secret incidents, teams. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/gitguardian updated: 2026-10-23 --- 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/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 ``` - 198 actions in one signed file - 101 read look, never change - 72 write create and update - 25 wait for a yes destructive, 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_key` GitGuardian personal access token or service account token (Dashboard > API > Personal access tokens / Service… - `host` Where 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 call check { 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 2026[api.gitguardian.com](https://api.gitguardian.com/v1/openapi.json) [api.gitguardian.com](https://api.gitguardian.com/docs) **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. - **101** read look, never change - **72** write create and update - **25** destructive wait 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. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `gitguardian.teams.list` List teams | List teams. | read | `identity.group.list` 262 connectors | | `gitguardian.scim_groups.list` List groups (SCIM) | List groups (SCIM). | read | `identity.group.list` 262 connectors | | `gitguardian.scim_users.list` List members (SCIM) | List members (SCIM). | read | `identity.user.list` 474 connectors | | `gitguardian.teams.delete` Delete a team | Delete a team. | destructive | `identity.group.delete` 181 connectors | | `gitguardian.scim_users.create` Create a member (SCIM) | Create a member (SCIM). | write | `identity.user.create` 262 connectors | | `gitguardian.sources.list` List sources | List sources. | read | `devops.repository.list` 28 connectors | | `gitguardian.members.list` List members | List members. | read | `work.workspace_member.list` 26 connectors | | `gitguardian.api_tokens.create` Create an API token. | Create an API token. | write | `identity.api_key.create` 100 connectors | | `gitguardian.api_tokens.list` List API tokens. | List API tokens. | read | `identity.api_key.list` 96 connectors | | `gitguardian.audit_logs.list` List audit Logs | List audit Logs. | read | `security.audit_log.list` 69 connectors | | `gitguardian.sources.get` Retrieve a source | Retrieve a source. | read | `devops.repository.get` 26 connectors | | `gitguardian.members.update` Update a member | Update a member. | write | `work.workspace_member.update` 16 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. Read read List our GitGuardian repositories with their visibility and default branch. calls `gitguardian.sources.list` 2. Write write Create a member (SCIM) in GitGuardian. Show me exactly what you will send before you save it. calls `gitguardian.scim_users.create` Governance for GitGuardian ## Destructive actions wait for a yes. 25 GitGuardian actions are destructive. These are all of them: - Delete a team `gitguardian.teams.delete` - Delete a member (SCIM) `gitguardian.scim_users.delete` - Revoke an API token. `gitguardian.api_tokens.delete` - Delete a secret incident note `gitguardian.secret_incidents.delete_note` - Delete an invitation `gitguardian.invitations.delete` - Delete a member `gitguardian.members.delete` - Deletion of a custom tag `gitguardian.custom_tags.delete` - Revoke the honeytoken `gitguardian.honeytokens.revoke` - Delete a group (SCIM) `gitguardian.scim_groups.delete` - Delete an IP allowlist rule `gitguardian.ip_allowlist.delete` - Cancel or decline a team request `gitguardian.teams.delete_request` - Delete a custom source `gitguardian.custom_sources.delete` - Revoke the current API token. `gitguardian.api_tokens.delete_self` - Delete a custom tags key `gitguardian.custom_tags.delete_key` - Delete a honeytoken note `gitguardian.honeytokens.delete_note` - Delete a team invitation `gitguardian.teams.delete_invitation` - Remove a member from a team `gitguardian.teams.delete_membership` - Remove an owner from an identity `gitguardian.nhi_identities.remove_owner` - Revoke a team's access to a resource `gitguardian.teams.revoke_resource_access` - Revoke a member's access to a resource `gitguardian.members.revoke_resource_access` - Revoke access to a secret incident `gitguardian.secret_incidents.revoke_access` - Remove the validity override of a secret `gitguardian.secrets.remove_validity_override` - Revoke an invitation's access to a resource `gitguardian.invitations.revoke_resource_access` - Delete a public secret incident note `gitguardian.public_secret_incidents.delete_note` - Unlink a ticket from a secret incident, public incident or honeytoken `gitguardian.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. do gitguardian.teams.delete confirm_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: "lead@example.com" }, { match: "gitguardian.scim_users.delete", approver: "lead@example.com" }, { match: "gitguardian.api_tokens.delete", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 198 GitGuardian actions - 198 actions page each page of a long list is one call - 55 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every GitGuardian action. 198 actions by area: the id your agent calls, what it does, and its effect. **Secret incidents 29** - `gitguardian.secret_incidents.assign` Assign a secret incident write - `gitguardian.secret_incidents.check_presence` Request a new presence check for a secret incident write - `gitguardian.secret_incidents.create_note` Create a secret incident note write - `gitguardian.secret_incidents.delete_note` Delete a secret incident note destructive - `gitguardian.secret_incidents.get` Retrieve a secret incident read - `gitguardian.secret_incidents.get_impacted_perimeter` Retrieve the impacted perimeter of a secret incident read - `gitguardian.secret_incidents.grant_access` Grant access to a secret incident write - `gitguardian.secret_incidents.ignore` Ignore a secret incident write - `gitguardian.secret_incidents.list` List secret incidents read - `gitguardian.secret_incidents.list_activity_logs` List activity logs of a secret incident read - `gitguardian.secret_incidents.list_invitation_access` List invitations with access to a secret incident read - `gitguardian.secret_incidents.list_invitations` List invitations having access to a Secret Incident read - `gitguardian.secret_incidents.list_leaks` Retrieve where a secret has been publicly leaked read - `gitguardian.secret_incidents.list_locations` List locations of a secret incident read - `gitguardian.secret_incidents.list_member_access` List members with access to a secret incident read - `gitguardian.secret_incidents.list_members` List members having access to a secret incident read - `gitguardian.secret_incidents.list_notes` List notes on a secret incident read - `gitguardian.secret_incidents.list_team_access` List teams with access to a secret incident read - `gitguardian.secret_incidents.list_teams` List teams having access to a secret incident read - `gitguardian.secret_incidents.list_vaults` Get vault information for a secret incident read - `gitguardian.secret_incidents.reopen` Reopen a secret incident write - `gitguardian.secret_incidents.resolve` Resolve a secret incident write - `gitguardian.secret_incidents.revoke_access` Revoke access to a secret incident destructive - `gitguardian.secret_incidents.share` Share a secret incident write - `gitguardian.secret_incidents.unassign` Unassign a secret incident write - `gitguardian.secret_incidents.unlink_destination_ticket` Unlink a ticket from a secret incident, public incident or honeytoken destructive - `gitguardian.secret_incidents.unshare` Unshare a secret incident write - `gitguardian.secret_incidents.update` Update a secret incident write - `gitguardian.secret_incidents.update_note` Update a secret incident note write **Teams 24** - `gitguardian.teams.accept_request` Accept a team request write - `gitguardian.teams.create` Create a team write - `gitguardian.teams.create_invitation` Create a team invitation write - `gitguardian.teams.create_membership` Add a member to a team write - `gitguardian.teams.create_request` Request access to a team write - `gitguardian.teams.delete` Delete a team destructive - `gitguardian.teams.delete_invitation` Delete a team invitation destructive - `gitguardian.teams.delete_membership` Remove a member from a team destructive - `gitguardian.teams.delete_request` Cancel or decline a team request destructive - `gitguardian.teams.get` Retrieve a team read - `gitguardian.teams.get_resource_access` Check team permission for a resource read - `gitguardian.teams.list` List teams read - `gitguardian.teams.list_invitations` List team invitations read - `gitguardian.teams.list_memberships` List team memberships read - `gitguardian.teams.list_requests` List team requests of a team read - `gitguardian.teams.list_secret_incident_access` List secret incidents a team has access to read - `gitguardian.teams.list_secret_incidents` List secret incidents of a team read - `gitguardian.teams.list_sources` List team sources read - `gitguardian.teams.revoke_resource_access` Revoke a team's access to a resource destructive - `gitguardian.teams.set_resource_access` Give a team access to a resource write - `gitguardian.teams.update` Update a team write - `gitguardian.teams.update_invitation` Update a team invitation write - `gitguardian.teams.update_membership` Update a team membership write - `gitguardian.teams.update_sources` Update a team perimeter write **Public secret incidents 20** - `gitguardian.public_secret_incidents.assign` Assign a public secret incident write - `gitguardian.public_secret_incidents.check_presence` Request a new presence check for a public secret incident write - `gitguardian.public_secret_incidents.create_note` Create a public secret incident note write - `gitguardian.public_secret_incidents.delete_note` Delete a public secret incident note destructive - `gitguardian.public_secret_incidents.get` Retrieve a public secret incident read - `gitguardian.public_secret_incidents.get_occurrence` Retrieve a public secret occurrence read - `gitguardian.public_secret_incidents.ignore` Ignore a public secret incident write - `gitguardian.public_secret_incidents.list` List public secret incidents read - `gitguardian.public_secret_incidents.list_activity_logs` List activity logs of a public secret incident read - `gitguardian.public_secret_incidents.list_notes` List notes on a public secret incident read - `gitguardian.public_secret_incidents.list_occurrences` List public secret occurrences read - `gitguardian.public_secret_incidents.list_vaults` Get vault information for a public secret incident read - `gitguardian.public_secret_incidents.reopen` Reopen a public secret incident write - `gitguardian.public_secret_incidents.resolve` Resolve a public secret incident write - `gitguardian.public_secret_incidents.set_custom_tags` Set custom tags of a public secret incident write - `gitguardian.public_secret_incidents.set_severity` Set severity of a public secret incident write - `gitguardian.public_secret_incidents.share` Share a public secret incident write - `gitguardian.public_secret_incidents.unassign` Unassign a public secret incident write - `gitguardian.public_secret_incidents.unshare` Unshare a public secret incident write - `gitguardian.public_secret_incidents.update_note` Update a public secret incident note write **Honeytokens 14** - `gitguardian.honeytokens.check_prefixes` Bulk prefix lookup for honeytoken HMSL hashes read - `gitguardian.honeytokens.create` Create a honeytoken write - `gitguardian.honeytokens.create_note` Create an honeytoken note write - `gitguardian.honeytokens.create_with_context` Create a honeytoken within a context write - `gitguardian.honeytokens.delete_note` Delete a honeytoken note destructive - `gitguardian.honeytokens.get` Retrieve a honeytoken read - `gitguardian.honeytokens.list` List honeytokens read - `gitguardian.honeytokens.list_activity_logs` List activity logs of a honeytoken read - `gitguardian.honeytokens.list_notes` List notes on an honeytoken read - `gitguardian.honeytokens.list_sources` List sources on an honeytoken read - `gitguardian.honeytokens.reset` Reset the honeytoken write - `gitguardian.honeytokens.revoke` Revoke the honeytoken destructive - `gitguardian.honeytokens.update` Update a honeytoken write - `gitguardian.honeytokens.update_note` Update a honeytoken note write **Members 13** - `gitguardian.members.delete` Delete a member destructive - `gitguardian.members.get` Retrieve a member read - `gitguardian.members.get_email_notifications` Retrieve a member's email settings read - `gitguardian.members.get_resource_access` Check member permission for a resource read - `gitguardian.members.list` List members read - `gitguardian.members.list_secret_incident_access` List secret incidents a member has access to read - `gitguardian.members.list_team_memberships` List team memberships of a member read - `gitguardian.members.list_team_requests` List team requests of a member read - `gitguardian.members.list_teams` List teams of a member read - `gitguardian.members.revoke_resource_access` Revoke a member's access to a resource destructive - `gitguardian.members.set_resource_access` Give a member access to a resource write - `gitguardian.members.update` Update a member write - `gitguardian.members.update_email_notifications` Update a member's email settings write **Invitations 9** - `gitguardian.invitations.create` Create an invitation write - `gitguardian.invitations.delete` Delete an invitation destructive - `gitguardian.invitations.get` Retrieve an invitation read - `gitguardian.invitations.get_resource_access` Check invitation permission for a resource read - `gitguardian.invitations.list` List invitations read - `gitguardian.invitations.list_secret_incident_access` List secret incidents an invitation has access to read - `gitguardian.invitations.resend` Resend an invitation write - `gitguardian.invitations.revoke_resource_access` Revoke an invitation's access to a resource destructive - `gitguardian.invitations.set_resource_access` Give an invitation access to a resource write **Custom tags 8** - `gitguardian.custom_tags.create` Create a custom tag write - `gitguardian.custom_tags.delete` Deletion of a custom tag destructive - `gitguardian.custom_tags.delete_key` Delete a custom tags key destructive - `gitguardian.custom_tags.get` Retrieve a custom tag read - `gitguardian.custom_tags.list` List custom tags read - `gitguardian.custom_tags.patch` Partial update of a Custom Tag write - `gitguardian.custom_tags.rename_key` Update custom tags key write - `gitguardian.custom_tags.update` Full Update of a Custom Tag write **Nhi identities 7** - `gitguardian.nhi_identities.add_owners` Add owners to an identity write - `gitguardian.nhi_identities.get` Retrieve an identity read - `gitguardian.nhi_identities.list` List identities read - `gitguardian.nhi_identities.list_locations` List the locations of an identity read - `gitguardian.nhi_identities.list_owners` List owners of an identity read - `gitguardian.nhi_identities.remove_owner` Remove an owner from an identity destructive - `gitguardian.nhi_identities.replace_owners` Replace the owners of an identity write **API tokens 6** - `gitguardian.api_tokens.create` Create an API token. write - `gitguardian.api_tokens.delete` Revoke an API token. destructive - `gitguardian.api_tokens.delete_self` Revoke the current API token. destructive - `gitguardian.api_tokens.get` Retrieve details of an API token. read - `gitguardian.api_tokens.get_self` Retrieve details of the current API token. read - `gitguardian.api_tokens.list` List API tokens. read **Scim groups 6** - `gitguardian.scim_groups.create` Create a group (SCIM) write - `gitguardian.scim_groups.delete` Delete a group (SCIM) destructive - `gitguardian.scim_groups.get` Detail of a group (SCIM) read - `gitguardian.scim_groups.list` List groups (SCIM) read - `gitguardian.scim_groups.patch` Partially update a group (SCIM) write - `gitguardian.scim_groups.replace` Update a group (SCIM) write **Scim users 6** - `gitguardian.scim_users.create` Create a member (SCIM) write - `gitguardian.scim_users.delete` Delete a member (SCIM) destructive - `gitguardian.scim_users.get` Detail of a member (SCIM) read - `gitguardian.scim_users.list` List members (SCIM) read - `gitguardian.scim_users.patch` Update (partial) of a member (SCIM) write - `gitguardian.scim_users.replace` Update of a member (SCIM) write **Sources 6** - `gitguardian.sources.get` Retrieve a source read - `gitguardian.sources.list` List sources read - `gitguardian.sources.list_locations` List locations of a source read - `gitguardian.sources.list_secret_incidents` List secret incidents of a source read - `gitguardian.sources.trigger_scans` Trigger scans on sources write - `gitguardian.sources.update` Update a source write **Custom sources 5** - `gitguardian.custom_sources.create` Create custom source write - `gitguardian.custom_sources.delete` Delete a custom source destructive - `gitguardian.custom_sources.get` Get a custom source read - `gitguardian.custom_sources.list` List custom sources read - `gitguardian.custom_sources.update` Update a custom source write **Ip allowlist 5** - `gitguardian.ip_allowlist.create` Create an IP allowlist rule write - `gitguardian.ip_allowlist.delete` Delete an IP allowlist rule destructive - `gitguardian.ip_allowlist.get` Retrieve an IP allowlist rule read - `gitguardian.ip_allowlist.list` List IP allowlist rules read - `gitguardian.ip_allowlist.update` Update an IP allowlist rule write **Secrets 4** - `gitguardian.secrets.get` Retrieve a secret value read - `gitguardian.secrets.get_validity` Get the validity of a secret read - `gitguardian.secrets.remove_validity_override` Remove the validity override of a secret destructive - `gitguardian.secrets.set_validity_override` Override the validity of a secret write **Health checks 3** - `gitguardian.health_checks.list` List health checks read - `gitguardian.health_checks.list_instance_history` List health check history for an instance read - `gitguardian.health_checks.trigger` Trigger a health check write **Honeytoken endpoint deployments 3** - `gitguardian.honeytoken_endpoint_deployments.confirm` Confirm a honeytoken endpoint deployment write - `gitguardian.honeytoken_endpoint_deployments.create` Reconcile (plant) honeytokens for a machine/user write - `gitguardian.honeytoken_endpoint_deployments.list` List a machine/user's honeytoken deployments (read-only) read **Scan 3** - `gitguardian.scan.content` Content scan read - `gitguardian.scan.create_incidents` Scan content and create incidents write - `gitguardian.scan.multiple` Multiple content scan read **Audit logs 2** - `gitguardian.audit_logs.list` List audit Logs read - `gitguardian.audit_logs.list_event_names` List audit log event names read **Check runs 2** - `gitguardian.check_runs.list` List GitHub check runs read - `gitguardian.check_runs.skip` Skip a GitHub check run write **Scans 2** - `gitguardian.scans.get` Retrieve a scan read - `gitguardian.scans.list` List scans read **Scim resource types 2** - `gitguardian.scim_resource_types.get` Resource Types (SCIM) read - `gitguardian.scim_resource_types.list` List Resource Types (SCIM) read **Scim schemas 2** - `gitguardian.scim_schemas.get` Schema (SCIM) read - `gitguardian.scim_schemas.list` List Schemas (SCIM) read **Secret detectors 2** - `gitguardian.secret_detectors.get` Get a secret detector read - `gitguardian.secret_detectors.list` List secret detectors read **Code fix requests 1** - `gitguardian.code_fix_requests.create` Create code fix requests write **Detector custom hosts 1** - `gitguardian.detector_custom_hosts.list` List detector custom hosts read **Developers 1** - `gitguardian.developers.list` List developers read **Health 1** - `gitguardian.health.get` API Health read **Honeytoken events 1** - `gitguardian.honeytoken_events.list` List all honeytokens events read **Ip addresses 1** - `gitguardian.ip_addresses.get` List GitGuardian IP addresses read **JWKS 1** - `gitguardian.jwks.get` List public keys used to sign JWTs. read **Nhi sources 1** - `gitguardian.nhi_sources.list` List sources read **Oauth server metadata 1** - `gitguardian.oauth_server_metadata.get` OAuth 2.0 Authorization Server Metadata. read **Oidc configuration 1** - `gitguardian.oidc_configuration.get` OpenID Connect discovery document. read **Quotas 1** - `gitguardian.quotas.get` Quota overview read **Remediation workflow 1** - `gitguardian.remediation_workflow.get` Retrieve the remediation workflow read **Scim service provider config 1** - `gitguardian.scim_service_provider_config.get` Service Provider Configuration (SCIM) read **Secret occurrences 1** - `gitguardian.secret_occurrences.list` List secret occurrences read **Severity rules 1** - `gitguardian.severity_rules.list` List severity rules read 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 - [Splunk SOAR 12](https://actionlake.com/connectors/splunk-soar) - [StrangeBee TheHive 12](https://actionlake.com/connectors/strangebee-thehive) - [Torq 12](https://actionlake.com/connectors/torq) - [Trend Vision One 12](https://actionlake.com/connectors/trend-vision-one) - [Expel Workbench 11](https://actionlake.com/connectors/expel-workbench) - [Aikido Security 9](https://actionlake.com/connectors/aikido-security) Joins with, on shared entities - [Cloudsmith 3](https://actionlake.com/connectors/cloudsmith) - [GitLab 2](https://actionlake.com/connectors/gitlab) - [Azure DevOps Services 2](https://actionlake.com/connectors/azure-devops-services) - [GitHub 2](https://actionlake.com/connectors/github) - [Gitea 2](https://actionlake.com/connectors/gitea) - [Forgejo 2](https://actionlake.com/connectors/forgejo) Browse - [All Identity & security connectors](https://actionlake.com/connectors/category/identity-and-security) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/gitguardian More: https://actionlake.com/llms.txt