Anonymized search log entries (query, timestamp, hits, response_time, cached).
AI agents call search_logs to retrieve information from Mcp Revelor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only analytics tool that retrieves historical search log data without side effects. It merely fetches and returns anonymized search metrics for monitoring and analysis purposes. No data modification, deletion, or code execution occurs. The low severity reflects that exposure of aggregated, anonymized search analytics poses minimal risk to the e-shop system.
From the tool's definition The tool retrieves 'Anonymized search log entries' including query, timestamp, hits, response_time, and cached status. It queries historical data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Anonymized search log entries (query, timestamp, hits, response_time, cached). It is categorised as a Read tool in the Mcp Revelor MCP Server, which means it retrieves data without modifying state.
Register the Mcp Revelor MCP server in PolicyLayer and add a rule for search_logs: 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 Mcp Revelor. Nothing to install.
search_logs 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 search_logs 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 search_logs. 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.
search_logs is provided by the Mcp Revelor MCP server (webotvurci-s-r-o/mcp-revelor). 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 →