AI agents use add_vector to create or update resources in LanceDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LanceDB MCP Server environment.
This tool modifies data by inserting vectors into a table, which is characteristic of Write category. It does not execute arbitrary code (Execute), delete data (Destructive), or involve financial transactions (Financial). Severity is medium because unauthorized vector additions could poison embeddings or degrade search quality, but the impact is limited to one table and is reversible.
From the tool's definition Tool name 'add_vector' and description 'Add a vector to a table' indicate data creation/modification. The action creates or appends new vector entries to a database table, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access add_vector gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LanceDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_vector:
{
"version": "1",
"default": "deny",
"tools": {
"add_vector": {
"limits": [
{
"counter": "add_vector_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_vector stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a vector to a table. It is categorised as a Write tool in the LanceDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LanceDB MCP Server MCP server in PolicyLayer and add a rule for add_vector: 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 MCP Server. Nothing to install.
add_vector 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 add_vector 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 add_vector. 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.
add_vector is provided by the LanceDB MCP Server MCP server (ryanlisse/lancedb_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LanceDB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 LanceDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.