create_pull_request_reply

THE RISK

Medium Risk

Why create_pull_request_reply needs a policy

The tool creates new data (a comment reply) without deleting or overwriting existing data, and without executing arbitrary code or moving financial resources. While comments can influence project decisions, the action itself is reversible (comments can be deleted). This qualifies as Write rather than Execute, as it doesn't run code or trigger external operations dependent on comment content.

From the tool's definition Tool description states 'Reply to a comment on a pull request' — this creates a new comment/reply, which is a reversible write operation that modifies the pull request discussion thread.

Documented attack patterns abuse exactly the kind of access create_pull_request_reply gives an agent:

POLICY

How to control create_pull_request_reply

PolicyLayer is an MCP gateway — it sits between your AI agents and AtomGit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_pull_request_reply:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_pull_request_reply": {
      "limits": [
        {
          "counter": "create_pull_request_reply_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_pull_request_reply 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.

Create a free account and register AtomGit MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AtomGit MCP Server tools

Destructive delete_issue_label Remove a label from an issue in a repository Write assign_issue Assign users to an issue in a AtomGit repository Write create_issue Create a new issue in a AtomGit repository Write create_issue_comment Create an issue comment in a AtomGit repository issue Write create_issue_labels Add labels to an issue in a repository Write create_pull_request Create a new pull request in a repository Write create_pull_request_comment Create a comment on a pull request Read check_if_user_is_assignable Check if a user can be assigned to an issue in a AtomGit repository

All 22 AtomGit MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_pull_request_reply

What does the create_pull_request_reply tool do? +

Reply to a comment on a pull request. It is categorised as a Write tool in the AtomGit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_pull_request_reply? +

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

What risk level is create_pull_request_reply? +

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

Can I rate-limit create_pull_request_reply? +

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

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

create_pull_request_reply is provided by the AtomGit MCP Server MCP server (kaiyuanxiaobing/atomgit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AtomGit MCP Server tool call.

Start from AtomGit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →