Get a single Kibana saved object by type and ID. This is a universal tool that can retrieve any type of saved object (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.) by its exact type and ID. Use this when you know the specific object...
Single-target operation
Part of the Kibana MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call vl_get_saved_object to retrieve information from Kibana without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though vl_get_saved_object only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
vl_get_saved_object:
rules:
- action: allowSee the full Kibana policy for all 16 tools.
Agents calling read-class tools like vl_get_saved_object have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get a single Kibana saved object by type and ID. This is a universal tool that can retrieve any type of saved object (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.) by its exact type and ID. Use this when you know the specific object you want to retrieve. PERFORMANCE: This is much faster than searching when you have the exact type and ID.. It is categorised as a Read tool in the Kibana MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for vl_get_saved_object. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kibana MCP server.
vl_get_saved_object 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 vl_get_saved_object 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.
Set action: deny in the Intercept policy for vl_get_saved_object. 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.
vl_get_saved_object 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.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept