Detections \u00b7 query customerDetectionActivityLogEntries. Variables: after, filter, first, order. Example variables: {\
AI agents call customer_detection_activity_log_entries 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 detection activity log entries without modifying any data. The query parameters (after, filter, first, order) are standard for pagination and filtering on read operations. No language suggesting data modification, deletion, execution, or financial operations is present. The blast radius of misuse is limited to unauthorized information access about detection activity.
From the tool's definition Tool name 'customer_detection_activity_log_entries' and description indicates it 'query customerDetectionActivityLogEntries' with query parameters (after, filter, first, order).
Attacks that exploit this kind of access
Detections \u00b7 query customerDetectionActivityLogEntries. Variables: after, filter, first, order. 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 customer_detection_activity_log_entries: 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.
customer_detection_activity_log_entries 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 customer_detection_activity_log_entries 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 customer_detection_activity_log_entries. 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.
customer_detection_activity_log_entries 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 →