AI agents use create-table to create or update resources in SQLite MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SQLite MCP Server environment.
CREATE TABLE modifies database schema irreversibly by adding new tables, but differs from Destructive tools because the table structure itself can be modified or the table can be dropped later (reversible at schema level). This is a Write operation—it creates structured data/objects.
From the tool's definition Tool name 'create-table' indicates a schema modification operation. Server context describes SQL query capabilities, and sibling tools include 'read-query' and 'write-query', establishing this server's SQL execution scope.
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 SQLite 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-table. It is categorised as a Write tool in the SQLite MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SQLite 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 SQLite 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 SQLite MCP Server MCP server (jacksteamdev/mcp-sqlite-bun-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SQLite 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.
6 SQLite MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.