add_incident_comment · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What add_incident_comment does on ReliaQuest GreyMatter MCP Server

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

WHY IT NEEDS A POLICY

Why add_incident_comment needs a policy

This tool creates or appends new comment data to an existing incident, which is a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).

From the tool's definition Tool name 'add_incident_comment' and description 'Add a comment to an incident' indicate creation of new comment data attached to an incident record. The IncidentCommentInput parameter confirms data is being written.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_incident_comment Rate-limited

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

FAQ

Questions about add_incident_comment

What does the add_incident_comment tool do? +

Add a comment to an incident. input: IncidentCommentInput { incidentId, comment }. Variables: after, filter, first, order, input. Example variables: {\. It is categorised as a Write tool in the ReliaQuest GreyMatter 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_incident_comment? +

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

What risk level is add_incident_comment? +

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

Can I rate-limit add_incident_comment? +

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

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

add_incident_comment is provided by the ReliaQuest GreyMatter MCP Server MCP server (space-c0wboy/reliaquest-greymatter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.