Permanently delete/drop an entire table from the PostgreSQL database, including all its data. Use with caution as this operation cannot be undone. Example: Delete a temporary_logs table that is no longer needed.
AI agents call delete_table to permanently remove resources in PostgreSQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly destroys entire tables and all their data with no undo capability. This is the most severe form of destructive action in databases. Even though the server is described as providing 'read-only access', this tool contradicts that claim and represents the highest-impact destructive operation possible. Misuse would result in permanent data loss affecting all records in a table.
From the tool's definition Tool description explicitly states 'Permanently delete/drop an entire table' and 'this operation cannot be undone', with the example showing deletion of a table.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access delete_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 delete_table:
{
"version": "1",
"default": "deny",
"hide": [
"delete_table"
]
}delete_table disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently delete/drop an entire table from the PostgreSQL database, including all its data. Use with caution as this operation cannot be undone. Example: Delete a temporary_logs table that is no longer needed. It is categorised as a Destructive tool in the PostgreSQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_table is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.