github_audit_repo

Single-call repo health check: README, license, branch protection, Dependabot, secret scanning, etc.

SERVERGithub SOURCEdkeeno/github-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-audit-repo.md

WHAT IT DOES

What github_audit_repo does on Github

AI agents call github_audit_repo to retrieve information from Github without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why github_audit_repo is rated Low

The tool performs a read-only audit of repository configuration and security settings. It retrieves and reports on health indicators without modifying any data. No writes, executions, deletions, or financial actions are implied.

From the tool's definition 'repo health check' covering README, license, branch protection, Dependabot, secret scanning — purely auditing/inspecting existing state

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_audit_repo 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_audit_repo, this is the rule to start with:

github_audit_repo Allowed

github_audit_repo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_audit_repo": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about github_audit_repo

What does the github_audit_repo tool do? +

Single-call repo health check: README, license, branch protection, Dependabot, secret scanning, etc. It is categorised as a Read tool in the Github MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_audit_repo? +

Register the Github MCP server in PolicyLayer and add a rule for github_audit_repo: 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_audit_repo? +

github_audit_repo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit github_audit_repo? +

Yes. Add a rate_limit block to the github_audit_repo 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_audit_repo completely? +

Set action: deny in the PolicyLayer policy for github_audit_repo. 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_audit_repo? +

github_audit_repo 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

Roll out MCP under one policy →Data exfiltration →MCP token cost →