search_by_service

Search logs filtered by service name, optionally with additional filters.

Server OpenSearch Logs MCP Server luis-dominguez-stori/mcp
Category Read
Risk class Low
Parameters 00 required

What search_by_service does on OpenSearch Logs MCP Server

AI agents call search_by_service 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.

Why search_by_service needs a policy

This tool retrieves log data based on service name and optional filter criteria. It has no side effects—it does not create, modify, delete, execute code, or move money. It is a straightforward read operation querying an existing data store. The low severity reflects the minimal blast radius if misused: an attacker could perform reconnaissance on application logs but cannot cause data loss or trigger external actions.

From the tool's definition Tool description states 'Search logs filtered by service name, optionally with additional filters.' The word 'Search' indicates a query operation with no modification or deletion of data.

Questions about search_by_service

What does the search_by_service tool do? +

Search logs filtered by service name, optionally with additional filters. It is categorised as a Read tool in the OpenSearch Logs MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_service? +

Register the OpenSearch Logs MCP Server MCP server in PolicyLayer and add a rule for search_by_service: 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.

What risk level is search_by_service? +

search_by_service is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_by_service? +

Yes. Add a rate_limit block to the search_by_service 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.

How do I block search_by_service completely? +

Set action: deny in the PolicyLayer policy for search_by_service. 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.

What MCP server provides search_by_service? +

search_by_service 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.