Update multiple Kibana saved objects in a single operation. Each object can be of different types and will be partially updated (only specified attributes changed). Supports all saved object types (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-ele...
High parameter count (11 properties); Single-target operation
Part of the Kibana MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use vl_bulk_update_saved_objects to create or modify resources in Kibana. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call vl_bulk_update_saved_objects repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Kibana.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
vl_bulk_update_saved_objects:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Kibana policy for all 16 tools.
Agents calling write-class tools like vl_bulk_update_saved_objects have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Update multiple Kibana saved objects in a single operation. Each object can be of different types and will be partially updated (only specified attributes changed). Supports all saved object types (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.). PERFORMANCE: More efficient than multiple single updates. Each object can have individual version control.. It is categorised as a Write tool in the Kibana MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for vl_bulk_update_saved_objects. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kibana MCP server.
vl_bulk_update_saved_objects is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vl_bulk_update_saved_objects 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_bulk_update_saved_objects. 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_bulk_update_saved_objects 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