github_enable_secret_scanning

Enable GitHub secret scanning + push protection on a repo (public repos free; private may require GHAS).

SERVERGithub SOURCEdkeeno/github-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-enable-secret-scanning.md

WHAT IT DOES

What github_enable_secret_scanning does on Github

AI agents use github_enable_secret_scanning to create or update resources in Github, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Github environment.

RISK

Why github_enable_secret_scanning is rated Medium

This tool modifies repository security settings rather than deleting or executing arbitrary operations. While it is a security-relevant change that affects how the repository handles secrets, the action is reversible and does not execute code, destroy data, or incur financial costs.

From the tool's definition Tool enables secret scanning and push protection features on a repository—it modifies repository configuration settings. The description explicitly states it 'enables' a feature, indicating a configuration change that is reversible (can be disabled later).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_enable_secret_scanning safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_enable_secret_scanning, this is the rule to start with:

github_enable_secret_scanning Rate-limited

github_enable_secret_scanning stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_enable_secret_scanning": {
      "limits": [
        {
          "counter": "github_enable_secret_scanning_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every github_enable_secret_scanning call is checked against it from then on.

FAQ

Questions about github_enable_secret_scanning

What does the github_enable_secret_scanning tool do? +

Enable GitHub secret scanning + push protection on a repo (public repos free; private may require GHAS). It is categorised as a Write tool in the Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on github_enable_secret_scanning? +

Register the Github MCP server in PolicyLayer and add a rule for github_enable_secret_scanning: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Github. Nothing to install.

What risk level is github_enable_secret_scanning? +

github_enable_secret_scanning is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit github_enable_secret_scanning? +

Yes. Add a rate_limit block to the github_enable_secret_scanning rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block github_enable_secret_scanning completely? +

Set action: deny in the PolicyLayer policy for github_enable_secret_scanning. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides github_enable_secret_scanning? +

github_enable_secret_scanning is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 69 Github tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →