List cases (with nested activity/children/comments connections). The OUTER list page size is first3 (set it to bound results, e.g. first3=25); first/first1/first2 page the nested connections. Variables: after, filter, first, order, after1, filter1, first1, order1, after2, filter2, first2, order2,...
AI agents call cases 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 lists cases with nested data (activity, children, comments). It is a read/query operation with no side effects. Severity is medium because it may expose sensitive incident response data including case details, comments, and activity logs.
From the tool's definition List cases (with nested activity/children/comments connections)
Attacks that exploit this kind of access
List cases (with nested activity/children/comments connections). The OUTER list page size is first3 (set it to bound results, e.g. first3=25); first/first1/first2 page the nested connections. Variables: after, filter, first, order, after1, filter1, first1, order1, after2, filter2, first2, order2, after3, filter3, first3, order3. 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 cases: 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.
cases 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 cases 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 cases. 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.
cases 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 →