Create a new table in the PostgreSQL database with specified columns and data types. Use this tool to define new database tables with custom schemas. Example: Create a users table with id, name, email, and created_at columns.
AI agents use create_table to create or update resources in PostgreSQL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PostgreSQL MCP Server environment.
This tool creates new database tables, which is a Write operation (data structure creation). It is not Destructive because table creation is reversible through deletion, and does not delete or irreversibly overwrite existing data. However, it carries high severity because uncontrolled table creation could consume database resources, alter schema integrity, or facilitate data exfiltration schemes.
From the tool's definition Tool description explicitly states 'Create a new table in the PostgreSQL database' and 'define new database tables with custom schemas'. The tool performs irreversible schema modification by adding new tables to the database structure.
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 PostgreSQL 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 in the PostgreSQL database with specified columns and data types. Use this tool to define new database tables with custom schemas. Example: Create a users table with id, name, email, and created_at columns. It is categorised as a Write tool in the PostgreSQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PostgreSQL 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 PostgreSQL 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 PostgreSQL MCP Server MCP server (vignesh-codes/ai-agents-mcp-pg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PostgreSQL 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 PostgreSQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.