github_prepare_feature_workflow · Github MCP: Risk & Policy

WHAT IT DOES

What github_prepare_feature_workflow does on Github

AI agents use github_prepare_feature_workflow 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.

WHY IT NEEDS A POLICY

Why github_prepare_feature_workflow needs a policy

This tool performs reversible data modification (branch creation and main updates) but does not push changes to remote, delete data, or trigger external deployments. The most severe action is branch creation, which is a Write operation.

From the tool's definition Tool creates a new feature branch and updates main, which are reversible write operations. Description explicitly states it 'check[s] status, update[s] main, and create[s] a new feature branch.' Creating branches modifies repository state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

github_prepare_feature_workflow Rate-limited

github_prepare_feature_workflow 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_prepare_feature_workflow": {
      "limits": [
        {
          "counter": "github_prepare_feature_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Github, so you can run agents against it safely.

FAQ

Questions about github_prepare_feature_workflow

What does the github_prepare_feature_workflow tool do? +

Check status, update main, and create a new feature branch. Does not push or create a PR. 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_prepare_feature_workflow? +

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

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

Can I rate-limit github_prepare_feature_workflow? +

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

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

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