Detections \u00b7 query customerDetectionActivityLogEntry. Variables: after, filter, first, order, id. Example variables: {\
AI agents call customer_detection_activity_log_entry 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 queries detection activity logs with filtering and pagination (after, first, order) parameters. While it performs a read operation (retrieval), the medium severity reflects that security detection logs may contain sensitive incident response information, operational intelligence, or customer threat data that could be misused by an agent if accessed without proper authorization or context.
From the tool's definition Tool name contains 'log_entry' and description indicates it 'query customerDetectionActivityLogEntry' with filtering and ordering parameters, suggesting data retrieval without modification.
Attacks that exploit this kind of access
Detections \u00b7 query customerDetectionActivityLogEntry. Variables: after, filter, first, order, id. 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_entry: 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_entry 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_entry 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_entry. 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_entry 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 →