Execute a DDL statement (CREATE TABLE, ALTER TABLE, DROP TABLE, etc.). Dangerous operations like DROP DATABASE, user management, and privilege changes are always blocked for safety.
AI agents invoke executeDDL to trigger actions in Postgresql. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes code-like operations (DDL statements) whose effects are irreversible and depend on the arguments provided. Although some dangerous operations (DROP DATABASE, user management) are blocked, the tool still permits DROP TABLE and ALTER TABLE operations that fundamentally alter database structure.
From the tool's definition Tool executes DDL statements including CREATE TABLE, ALTER TABLE, DROP TABLE. While DROP DATABASE and privilege changes are blocked, the tool still permits destructive operations like DROP TABLE and structural modifications like ALTER TABLE that modify…
Attacks that exploit this kind of access
Execute a DDL statement (CREATE TABLE, ALTER TABLE, DROP TABLE, etc.). Dangerous operations like DROP DATABASE, user management, and privilege changes are always blocked for safety. It is categorised as a Execute tool in the Postgresql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Postgresql MCP server in PolicyLayer and add a rule for executeDDL: 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. Nothing to install.
executeDDL is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the executeDDL 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 executeDDL. 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.
executeDDL is provided by the Postgresql MCP server (vnikhilbuddhavarapu/postgresql-mcp). 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 →