commit_dialog · Prompts MCP: Risk & Policy

WHAT IT DOES

What commit_dialog does on Prompts

AI agents invoke commit_dialog to trigger actions in Prompts. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why commit_dialog needs a policy

This tool executes a git commit operation, which is an external VCS action that modifies repository history. While commits can technically be amended or reverted, the act of committing is an external operation with side effects beyond simple data writes. It falls under Execute as it triggers a git operation whose effects depend on the working state and arguments provided.

From the tool's definition 手动触发一次 git commit — manually triggers a git commit, optionally specifying files or committing all changes

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

commit_dialog Rate-limited

commit_dialog stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "commit_dialog": {
      "limits": [
        {
          "counter": "commit_dialog_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about commit_dialog

What does the commit_dialog tool do? +

【手动提交】手动触发一次 git commit。可指定要提交的文件，不指定则提交所有变更。. It is categorised as a Execute tool in the Prompts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on commit_dialog? +

Register the Prompts MCP server in PolicyLayer and add a rule for commit_dialog: 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 Prompts. Nothing to install.

What risk level is commit_dialog? +

commit_dialog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit commit_dialog? +

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

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

commit_dialog is provided by the Prompts MCP server (thana0623/pmcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.