AI agents use create_table to create or update resources in MCP SQLite Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP SQLite Server environment.
This tool creates a new table, which is a reversible structural modification to the database. It is Write (not Destructive) because table creation can be undone via deletion. It has medium severity because an AI agent could create numerous tables consuming resources, or interfere with expected database schemas, but the effect is recoverable.
From the tool's definition Tool name is 'create_table' and description states 'Create a new table in the SQLite database', indicating it creates new data structures in a persistent store.
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 MCP SQLite 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 in the SQLite database. It is categorised as a Write tool in the MCP SQLite Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP SQLite 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 MCP SQLite 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 MCP SQLite Server MCP server (johnnyoshika/mcp-server-sqlite-npx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP SQLite 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.
5 MCP SQLite Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.