List deployed detection rules across GreyMatter integrations (includes MITRE ATT&CK mapping where available). Variables: after, detectionRuleOrder, filter, first. Example variables: {\
AI agents call detection_rules 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 detection rules from the GreyMatter platform without modifying, executing, or deleting anything. It is a read-only query operation with no side effects. The inclusion of MITRE ATT&CK mapping in the output does not change the nature of the operation. No data is created, modified, or destroyed.
From the tool's definition Tool name 'detection_rules' with description 'List deployed detection rules' indicates data retrieval. Parameters (after, detectionRuleOrder, filter, first) are consistent with pagination and filtering of query results, typical of list/get operations.
Attacks that exploit this kind of access
List deployed detection rules across GreyMatter integrations (includes MITRE ATT&CK mapping where available). Variables: after, detectionRuleOrder, filter, first. 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 detection_rules: 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.
detection_rules 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 detection_rules 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 detection_rules. 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.
detection_rules 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 →