assign_incident · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What assign_incident does on ReliaQuest GreyMatter MCP Server

AI agents use assign_incident 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 assign_incident needs a policy

This tool creates or modifies data reversibly by changing incident assignment metadata. An AI agent could inadvertently assign critical incidents to wrong users, disrupting incident response workflows, but the action is not financial, destructive (data is not deleted), or executing arbitrary code. The impact is operational and reversible through reassignment.

From the tool's definition Tool description states 'Assign an incident to a GreyMatter user' with inputs incidentId and assigneeId, which modifies the assignment state of an incident record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_incident Rate-limited

assign_incident 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": {
    "assign_incident": {
      "limits": [
        {
          "counter": "assign_incident_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 assign_incident

What does the assign_incident tool do? +

Assign an incident to a GreyMatter user. input: AssignIncidentInput { incidentId, assigneeId }. Resolve assigneeId via the customer/users query. Variables: 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 assign_incident? +

Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for assign_incident: 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 assign_incident? +

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

Can I rate-limit assign_incident? +

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

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

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