List all data views (index patterns) in Kibana
AI agents call list_data_views to retrieve information from Kibana 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 and enumerates Kibana data views without creating, modifying, deleting, or executing operations. It is a straightforward read operation that returns information about existing resources. The blast radius is minimal—an AI agent calling this tool cannot cause harm beyond potential information disclosure of available data view names, which is typically non-sensitive metadata.
From the tool's definition Tool name 'list_data_views' and description 'List all data views (index patterns) in Kibana' indicate a query/retrieval operation with no modification or execution of side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all data views (index patterns) in Kibana. It is categorised as a Read tool in the Kibana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kibana MCP Server MCP server in PolicyLayer and add a rule for list_data_views: 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.
list_data_views 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 list_data_views 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 list_data_views. 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.
list_data_views 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.
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 →