Add vectors with metadata to a LanceDB table. Creates the table if it doesn
AI agents use vector_add to create or update resources in LanceDB Node — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LanceDB Node environment.
This tool creates or modifies data in a vector database in a reversible manner. New vectors can be added, updated, or removed without permanent destruction. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool adds vectors with metadata to a LanceDB table and can create the table if it doesn't exist. The description explicitly states 'Add vectors' and 'Creates the table if it doesn', indicating data creation and modification capabilities.
Attacks that exploit this kind of access
Add vectors with metadata to a LanceDB table. Creates the table if it doesn. It is categorised as a Write tool in the LanceDB Node MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LanceDB Node MCP server in PolicyLayer and add a rule for vector_add: 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 LanceDB Node. Nothing to install.
vector_add 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 vector_add 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 vector_add. 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.
vector_add is provided by the LanceDB Node MCP server (vurtnec/mcp-lancedb-node). 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 →