Resolve or cancel an incident. request: CloseIncidentRequest { incidentId, state (RESOLVED or CANCELLED), closeCode, closeNote }. Incident close codes: CUSTOMER_ANOMALOUS_SAFE, CUSTOMER_FALSE_POSITIVE, CUSTOMER_TRUE_POSITIVE, FALSE_POSITIVE_CREATE_TUNING_TICKET, CUSTOMER_SECURITY_CONTROL_TESTING,...
AI agents use close_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.
This tool modifies incident state and metadata (closeCode, closeNote) in the ReliaQuest GreyMatter incident response platform. While it doesn't delete data (which would be Destructive), it permanently changes incident status in a security incident management system.
From the tool's definition The tool description states it can 'Resolve or cancel an incident' with parameters for incidentId, state (RESOLVED or CANCELLED), and closeCode. These are clear write operations that modify incident records in the system.
Attacks that exploit this kind of access
Resolve or cancel an incident. request: CloseIncidentRequest { incidentId, state (RESOLVED or CANCELLED), closeCode, closeNote }. Incident close codes: CUSTOMER_ANOMALOUS_SAFE, CUSTOMER_FALSE_POSITIVE, CUSTOMER_TRUE_POSITIVE, FALSE_POSITIVE_CREATE_TUNING_TICKET, CUSTOMER_SECURITY_CONTROL_TESTING, CUSTOMER_CANCELLED. Variables: request. 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.
Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for close_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.
close_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_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.
Set action: deny in the PolicyLayer policy for close_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.
close_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →