search_logs · Kibana MCP Server MCP: Risk & Policy

WHAT IT DOES

What search_logs does on Kibana MCP Server

AI agents invoke search_logs to trigger actions in Kibana MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why search_logs needs a policy

Although the tool is described as part of a 'read-only' server, it executes arbitrary Elasticsearch Query DSL, which can include complex aggregations, script queries, and potentially expensive operations. The free-form nature of Elasticsearch DSL means an AI agent could craft queries that consume significant resources or expose sensitive data across indices.

From the tool's definition Search Elasticsearch data through Kibana using Elasticsearch query DSL

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

search_logs Rate-limited

search_logs stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_logs": {
      "limits": [
        {
          "counter": "search_logs_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kibana MCP Server, so you can run agents against it safely.

FAQ

Questions about search_logs

What does the search_logs tool do? +

Search Elasticsearch data through Kibana using Elasticsearch query DSL. It is categorised as a Execute tool in the Kibana MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on search_logs? +

Register the Kibana MCP Server 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 Kibana MCP Server. Nothing to install.

What risk level is search_logs? +

search_logs is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit search_logs? +

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.

How do I block search_logs completely? +

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.

What MCP server provides search_logs? +

search_logs is provided by the Kibana MCP Server MCP server (jerrelblankenship/jb-kibana-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.