# add_comment

Add a comment to an existing issue

Agent View of the PolicyLayer registry record for `add_comment`. HTML page: https://policylayer.com/tools/1broseidon-mcp-jira-server/add-comment

## Facts

- Tool: `add_comment`
- Server: Mcp Jira (`1broseidon/mcp-jira-server`) — https://policylayer.com/tools/1broseidon-mcp-jira-server.md
- Homepage: https://github.com/1broseidon/mcp-jira-server
- Risk category: Write (Medium risk)
- Registry record: grade D, 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": "add_comment",
    "arguments": {}
  }
}
```

## Why add_comment is rated Medium

This tool creates new data (a comment) in a Jira issue but does not modify the issue itself, delete anything, execute code, or move money. The action is reversible—comments can be removed or edited. Therefore, it falls squarely into the Write category with low severity, as comment spam or off-topic comments are inconvenient but easily remediated and have minimal blast radius.

From the tool's own definition: "Tool name 'add_comment' and description 'Add a comment to an existing issue' indicate data creation that is reversible and non-destructive. Comments can be edited or deleted by appropriate users."

## Use case

AI agents use add_comment to create or update resources in Mcp Jira, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jira environment.

## Recommended policy (PolicyLayer)

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

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

## Other tools on Mcp Jira (5)

- `delete_issue` — Destructive — https://policylayer.com/tools/1broseidon-mcp-jira-server/delete-issue.md
- `get_issue` — Read — https://policylayer.com/tools/1broseidon-mcp-jira-server/get-issue.md
- `list_issues` — Read — https://policylayer.com/tools/1broseidon-mcp-jira-server/list-issues.md
- `create_issue` — Write — https://policylayer.com/tools/1broseidon-mcp-jira-server/create-issue.md
- `update_issue` — Write — https://policylayer.com/tools/1broseidon-mcp-jira-server/update-issue.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=1broseidon-mcp-jira-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1broseidon-mcp-jira-server