Home / Servers / GitHub API / secret_scanning_create_push_protection_bypass
Create a push protection bypass
An MCP tool from the GitHub API server, hosted on mcp.hjlabs.in.
Create a push protection bypass Creates a bypass for a previously push protected secret. The authenticated user must be the original author of the committed secret. OAuth app tokens and personal access tokens (classic) need the… [POST /repos/{owner}/{repo}/secret-scanning/push-protection-bypasses]
Name on the gateway: github_api__secret_scanning_create_push_protection_bypass · may change things.
Parameters
| Name | Type | Description |
|---|---|---|
owner required | string | The account owner of the repository. The name is not case… |
repo required | string | The name of the repository without the .git extension. The… |
reason required | false_positive | used_in_tests | will_fix_later | The reason for bypassing push protection. |
placeholder_id required | string | The ID of the push protection bypass placeholder. This value is returned on… |
How to call it
Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:
{
"name": "github_api__secret_scanning_create_push_protection_bypass",
"arguments": {
"owner": "…",
"repo": "…",
"reason": "…",
"placeholder_id": "…"
}
}Or connect the GitHub API server directly, which lists 1,221 tools including this one:
claude mcp add --transport http hj-github-api https://mcp.hjlabs.in/mcp/github-api \
--header "Authorization: Bearer YOUR_API_KEY"Try asking
Use the create a push protection bypass tool with owner set to ….