Export a dashboard with all its dependencies (visualizations, data views, etc.)
AI agents call export_dashboard 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.
Exporting a dashboard retrieves and packages existing data without modifying or deleting anything. The server is described as providing read-only resources, and exporting is a non-destructive operation that simply reads and bundles dashboard configurations and dependencies.
From the tool's definition Export a dashboard with all its dependencies (visualizations, data views, etc.) — this is a read/export operation retrieving existing data; the server description also confirms 'read-only resources'
Attacks that exploit this kind of access
Export a dashboard with all its dependencies (visualizations, data views, etc.). 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 export_dashboard: 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.
export_dashboard 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 export_dashboard 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 export_dashboard. 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.
export_dashboard 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 →