Create a new table in the SQLite database
AI agents use create_table to create or update resources in Server Puppeteer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Server Puppeteer environment.
This tool creates a new table in SQLite, which is a write operation that modifies the database schema. It is reversible (the table can be dropped), so it does not qualify as Destructive. The severity is medium because creating tables can impact database structure and potentially consume resources, but the effect is limited to schema modification without data loss.
From the tool's definition Tool description states: 'Create a new table in the SQLite database'. The verb 'Create' indicates data structure creation, which is a reversible write operation.
Attacks that exploit this kind of access
Create a new table in the SQLite database. It is categorised as a Write tool in the Server Puppeteer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Server Puppeteer 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 Server Puppeteer. 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 Server Puppeteer MCP server (@hisma/server-puppeteer). 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 →