create_issue_comment · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_issue_comment does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why create_issue_comment needs a policy

Creating an issue comment modifies issue state by adding a new comment, which is a reversible write operation. While the description is empty, the name and context from sibling tools make the function clear. The severity is medium because a malicious agent could spam comments, post sensitive information, or harass users, but the operation is reversible (comments can be deleted).

From the tool's definition Tool name 'create_issue_comment' indicates creation of a new comment resource on a GitHub issue. This is consistent with sibling tools like 'create_issue', 'create_gist', and 'create_pull_request' which are all Write operations that reversibly create data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_issue_comment Rate-limited

create_issue_comment 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": {
    "create_issue_comment": {
      "limits": [
        {
          "counter": "create_issue_comment_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about create_issue_comment

What does the create_issue_comment tool do? +

create_issue_comment. It is categorised as a Write tool in the GitHub 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_issue_comment? +

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

What risk level is create_issue_comment? +

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

Can I rate-limit create_issue_comment? +

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

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

create_issue_comment is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.