update_incident_state · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What update_incident_state does on ReliaQuest GreyMatter MCP Server

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

This tool updates/modifies an existing incident's state, which is a reversible write operation. Incidents in a security platform are critical records; changing their state (e.g., open/closed/acknowledged) could disrupt incident response workflows if misused, warranting high severity. No indication of irreversible deletion or financial impact.

From the tool's definition "Change an incident" — modifies the state of an existing incident record

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_incident_state Rate-limited

update_incident_state 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": {
    "update_incident_state": {
      "limits": [
        {
          "counter": "update_incident_state_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 update_incident_state

What does the update_incident_state tool do? +

Change an incident. 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 update_incident_state? +

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

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

Can I rate-limit update_incident_state? +

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

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

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