High Risk →

execute_kb_api

Execute a custom API request for Kibana with multi-space support

Accepts file system path (path); Accepts raw HTML/template content (body)

Part of the Kibana MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke execute_kb_api to trigger processes or run actions in Kibana. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

execute_kb_api can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

kibana.yaml
tools:
  execute_kb_api:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Kibana policy for all 16 tools.

Tool Name execute_kb_api
Category Execute
MCP Server Kibana MCP Server
Risk Level High

View all 16 tools →

Agents calling execute-class tools like execute_kb_api have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

execute_kb_api is one of the high-risk operations in Kibana. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the execute_kb_api tool do? +

Execute a custom API request for Kibana with multi-space support. It is categorised as a Execute tool in the Kibana MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_kb_api? +

Add a rule in your Intercept YAML policy under the tools section for execute_kb_api. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kibana MCP server.

What risk level is execute_kb_api? +

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

Can I rate-limit execute_kb_api? +

Yes. Add a rate_limit block to the execute_kb_api rule in your Intercept 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 execute_kb_api completely? +

Set action: deny in the Intercept policy for execute_kb_api. 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 execute_kb_api? +

execute_kb_api is provided by the Kibana MCP server (@tocharianou/mcp-server-kibana). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Kibana

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.