Create new tables in the database
AI agents use create_table to create or update resources in MCP Database Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Database Server environment.
Creating tables is a Write operation—it creates new database structures that can be reversed through drop_table (present on this server). While it modifies the database schema, the action is not destructive (data is not deleted) and does not involve financial operations. Severity is medium because schema changes could disrupt applications if misused by an agent, but the impact is typically manageable and reversible.
From the tool's definition Tool name is 'create_table' and description states 'Create new tables in the database'. This is a data creation operation that modifies the schema reversibly.
Attacks that exploit this kind of access
Create new tables in the database. It is categorised as a Write tool in the MCP Database Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Database 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 Database 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 Database Server MCP server (msathiyakeerthi/mcp-database-server). 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 →