add_issue_comment · GitHub See MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_issue_comment does on GitHub See MCP Server

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

WHY IT NEEDS A POLICY

Why add_issue_comment needs a policy

This tool creates new data (a comment) on a GitHub issue, which is a reversible modification—comments can be edited or deleted. It does not execute arbitrary code, delete data permanently, or move money. It falls squarely into the Write category.

From the tool's definition Tool name 'add_issue_comment' and description 'Add a comment to an issue' indicate creation of new content (a comment) that modifies the state of a GitHub issue reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_issue_comment Rate-limited

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

FAQ

Questions about add_issue_comment

What does the add_issue_comment tool do? +

Add a comment to an issue. It is categorised as a Write tool in the GitHub See 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 add_issue_comment? +

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

What risk level is add_issue_comment? +

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

Can I rate-limit add_issue_comment? +

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

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

add_issue_comment is provided by the GitHub See MCP Server MCP server (jesusmaster/github-see-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.