# generate_commit

Generate a conventional commit message for my staged changes.

Agent View of the PolicyLayer registry record for `generate_commit`. HTML page: https://policylayer.com/tools/0010aor-mcp-pr-pilot/generate-commit

## Facts

- Tool: `generate_commit`
- Server: MCP Server PR Pilot (`0010aor/mcp-pr-pilot`) — https://policylayer.com/tools/0010aor-mcp-pr-pilot.md
- Homepage: https://github.com/0010aor/mcp-pr-pilot
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "generate_commit",
    "arguments": {}
  }
}
```

## Why generate_commit is rated Medium

This tool generates text output (a commit message) based on git diffs but does not directly execute git commands, modify the repository, or have irreversible side effects. The actual commit operation would be performed separately by the user.

From the tool's own definition: "Tool 'generate_commit' generates a conventional commit message for staged changes. The description indicates it creates (generates) a commit message artifact based on input code diffs, which is a write operation that creates new data (the commit message text)."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP Server PR Pilot:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_commit": {
      "limits": [
        {
          "counter": "generate_commit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on MCP Server PR Pilot (3)

- `review_changes` — Read — https://policylayer.com/tools/0010aor-mcp-pr-pilot/review-changes.md
- `summarize_pr` — Read — https://policylayer.com/tools/0010aor-mcp-pr-pilot/summarize-pr.md
- `generate_docs` — Write — https://policylayer.com/tools/0010aor-mcp-pr-pilot/generate-docs.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0010aor-mcp-pr-pilot · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0010aor-mcp-pr-pilot