List all Kibana visualizations
AI agents call list_visualizations 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 queries and returns metadata about existing visualizations without modifying, executing code, deleting, or affecting financial systems. It is a straightforward list/fetch operation typical of Read category tools. The low severity reflects minimal blast radius—an AI agent listing visualizations poses no risk of unintended data loss, code execution, or system damage.
From the tool's definition Tool name 'list_visualizations' and description 'List all Kibana visualizations' indicate a retrieval operation with no data modification. The server description confirms this is part of 'read-only resources'.
Attacks that exploit this kind of access
List all Kibana visualizations. 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_visualizations: 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_visualizations 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_visualizations 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_visualizations. 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_visualizations 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 →