release_incident · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What release_incident does on ReliaQuest GreyMatter MCP Server

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

This tool modifies incident data in a reversible manner by changing incident state (releasing from hold/assignment), which is characteristic of Write operations. It does not delete data (Destructive), execute arbitrary code (Execute), create financial transactions (Financial), or merely retrieve data (Read).

From the tool's definition Tool name 'release_incident' and description identify it as a mutation operation (GraphQL mutation) that modifies incident state by releasing/unlocking an incident from its current assignment or hold status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

release_incident Rate-limited

release_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": {
    "release_incident": {
      "limits": [
        {
          "counter": "release_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 release_incident

What does the release_incident tool do? +

Incidents \u00b7 mutation releaseIncident. Variables: id. 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 release_incident? +

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

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

Can I rate-limit release_incident? +

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

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

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