Search for error logs, optionally filtered by service or additional query.
AI agents call search_errors to retrieve information from OpenSearch Logs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query against log data in OpenSearch. It retrieves error logs based on filters but does not create, modify, delete, or execute external operations. The blast radius of misuse is limited to information disclosure (reading logs that may contain sensitive data), which is a standard Read category risk at low severity since logs are typically designed to be queryable by authorized services.
From the tool's definition Tool name 'search_errors' and description 'Search for error logs' indicate a query operation that retrieves existing log data without modification.
Attacks that exploit this kind of access
Search for error logs, optionally filtered by service or additional query. It is categorised as a Read tool in the OpenSearch Logs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenSearch Logs MCP Server MCP server in PolicyLayer and add a rule for search_errors: 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 OpenSearch Logs MCP Server. Nothing to install.
search_errors 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_errors 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_errors. 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_errors is provided by the OpenSearch Logs MCP Server MCP server (luis-dominguez-stori/mcp). 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 →