unassign_drp_alert · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What unassign_drp_alert does on ReliaQuest GreyMatter MCP Server

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

This tool performs a reversible modification to alert assignment metadata within the incident response platform. Unassigning an alert is a write operation that changes state but does not delete data or trigger external actions. It has a medium blast radius—misuse could reassign critical security alerts, disrupting incident response workflows, but the action is reversible and does not destroy data or move funds.

From the tool's definition Tool name 'unassign_drp_alert' and description indicating it is a 'mutation' that modifies DRP Alert assignment state. GraphQL mutations are write operations that change data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unassign_drp_alert Rate-limited

unassign_drp_alert 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": {
    "unassign_drp_alert": {
      "limits": [
        {
          "counter": "unassign_drp_alert_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 unassign_drp_alert

What does the unassign_drp_alert tool do? +

DRP Alerts \u00b7 mutation unassignDRPAlert. 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 unassign_drp_alert? +

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

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

Can I rate-limit unassign_drp_alert? +

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

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

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