Search logs by a specific field and value.
AI agents call search_by_field 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 retrieves log data based on field-value filtering. It has no side effects, does not modify or delete data, and does not execute arbitrary code. The blast radius of misuse is minimal — an agent could over-query or access sensitive log content, but cannot change system state. Read operations on logs present only informational risk, classified as low severity.
From the tool's definition Tool is described as 'Search logs by a specific field and value' — a straightforward read operation that queries existing data without modification.
Attacks that exploit this kind of access
Search logs by a specific field and value. 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_by_field: 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_by_field 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_by_field 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_by_field. 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_by_field 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 →