List security incidents with filtering (state, severity, updated time range) and ordering. Relay-paginated (edges/pageInfo/totalCount). Common states: PENDING_CUSTOMER, PENDING_RQ, RESOLVED, CANCELLED. Variables: after, first, incidentFilter, incidentOrder. Example variables: {\
AI agents call incidents to retrieve information from ReliaQuest GreyMatter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries incident data with various filter and sorting options but does not create, modify, delete, execute code, or perform financial transactions. While it accesses sensitive security incident information (which warrants medium severity due to potential information disclosure), the operation itself is a straightforward read-only query.
From the tool's definition Tool name is 'incidents' and description states it 'List security incidents with filtering...ordering' and 'Relay-paginated'. The verbs 'list' and 'filtering' indicate retrieval operations with no side effects.
Attacks that exploit this kind of access
List security incidents with filtering (state, severity, updated time range) and ordering. Relay-paginated (edges/pageInfo/totalCount). Common states: PENDING_CUSTOMER, PENDING_RQ, RESOLVED, CANCELLED. Variables: after, first, incidentFilter, incidentOrder. Example variables: {\. It is categorised as a Read tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for incidents: 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.
incidents is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the incidents 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 incidents. 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.
incidents 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 →