Push a multimodal content_list (RAG-Anything style) into a Lens knowledge base. The content_list_json must be a JSON array of items with type=text|image|table|equation and associated fields (e.g. img_path, table_body, latex).
AI agents use push_multimodal_content_list_to_lens_kb to create or update resources in Lens — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lens environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Logical document name (e.g. original file name) |
language | string | — | Language code (e.g. pt, en) |
source_id | string | — | Optional source identifier/path (e.g. original file path or external ID) |
source_type | string | — | Lens Document.source_type (file, url, text, api, mcp) |
content_type | string | — | MIME type of the underlying source (e.g. application/pdf, image/png) |
metadata_json | string | — | Optional JSON string with additional document-level metadata |
content_list_json | string | Yes | JSON string with the multimodal content_list array (RAG-Anything style). Example: [{"type": "image", "img_path": "https://...", "image_caption": ["Figure 1: ... |
knowledge_base_id | string | Yes | Knowledge base UUID (from list_knowledge_bases) |
Parameters from the server's own tool schema.
This tool creates or modifies data in a knowledge base by pushing new multimodal content items. The action is reversible (content can be updated or removed later), making it a Write operation rather than Destructive.
From the tool's definition Tool name contains 'push' and description states 'Push a multimodal content_list into a Lens knowledge base', indicating creation/modification of knowledge base content.
Attacks that exploit this kind of access
Push a multimodal content_list (RAG-Anything style) into a Lens knowledge base. The content_list_json must be a JSON array of items with type=text|image|table|equation and associated fields (e.g. img_path, table_body, latex). It is categorised as a Write tool in the Lens MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
push_multimodal_content_list_to_lens_kb accepts 8 parameters: name, language, source_id, source_type, content_type, metadata_json, content_list_json, knowledge_base_id. Required: name, content_list_json, knowledge_base_id. The full parameter table on this page comes from the server's own tool schema.
Register the Lens MCP server in PolicyLayer and add a rule for push_multimodal_content_list_to_lens_kb: 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 Lens. Nothing to install.
push_multimodal_content_list_to_lens_kb 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 push_multimodal_content_list_to_lens_kb 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 push_multimodal_content_list_to_lens_kb. 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.
push_multimodal_content_list_to_lens_kb is provided by the Lens MCP server (lens-mcp-server). 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 →