OpenSearch/search engine status: latency p50/p95/p99, indexed product count, cluster health.
AI agents call search_engine_status 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 tool retrieves monitoring and diagnostic data about the search infrastructure without causing side effects, creating, modifying, deleting, or executing operations. It is purely observational and informational.
From the tool's definition Tool returns operational metrics: 'latency p50/p95/p99, indexed product count, cluster health' — all read-only status information with no modification or execution capability.
Attacks that exploit this kind of access
OpenSearch/search engine status: latency p50/p95/p99, indexed product count, cluster health. 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_engine_status: 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_engine_status 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_engine_status 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_engine_status. 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_engine_status 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 →