github_enable_pages

Enable GitHub Pages on the repo, served from the given branch + path.

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-pages.md

WHAT IT DOES

What github_enable_pages does on Github

AI agents use github_enable_pages 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_pages is rated Medium

This tool creates or modifies repository configuration settings (enabling GitHub Pages service) rather than deleting data or executing arbitrary code. While it does expose the repository content as a public website, this is a reversible Write operation—Pages can be disabled, branches changed, or paths reconfigured without data loss.

From the tool's definition Tool enables GitHub Pages on a repository by configuring it to serve from a specified branch and path. This modifies repository settings and enables a public-facing web service, which is a reversible configuration change.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

github_enable_pages Rate-limited

github_enable_pages 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_pages": {
      "limits": [
        {
          "counter": "github_enable_pages_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_pages call is checked against it from then on.

FAQ

Questions about github_enable_pages

What does the github_enable_pages tool do? +

Enable GitHub Pages on the repo, served from the given branch + path. 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_pages? +

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

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

Can I rate-limit github_enable_pages? +

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

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

github_enable_pages 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 →