AI agents use create_table 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.
Creating a table is a reversible Write operation—it establishes new data storage but can be undone by dropping the table. It does not execute arbitrary code, delete existing data irreversibly, or move money. The severity is medium because misuse could create unwanted tables consuming storage resources and cluttering the database, but the action itself is non-destructive and can be remedied.
From the tool's definition Tool name is 'create_table' and description states 'Create a new table'. In a vector database context, this creates a new data structure/collection for storing embeddings.
Documented attack patterns abuse exactly the kind of access create_table 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 create_table:
{
"version": "1",
"default": "deny",
"tools": {
"create_table": {
"limits": [
{
"counter": "create_table_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_table 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.
Create a new 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 create_table: 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.
create_table 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 create_table 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 create_table. 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.
create_table 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.