pg_role_drop
Drop a PostgreSQL role. Use ifExists (default: true) to skip gracefully if the role does not exist.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-role-drop.md
What pg_role_drop does on PostgreSQL MCP Server
AI agents call pg_role_drop 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.
Why pg_role_drop is rated Critical
Dropping a PostgreSQL role is an irreversible action that deletes a database object. This cannot be undone without restore-from-backup procedures. The tool permits deletion of authentication/authorization objects that may affect multiple users and applications. While the ifExists parameter allows graceful handling of non-existent roles, the core function remains destructive.
From the tool's definition Tool name 'pg_role_drop' and description 'Drop a PostgreSQL role' — 'drop' is an explicit destructive operation that irreversibly removes a role from the database.
Attacks that exploit this kind of access
The rule that runs pg_role_drop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and PostgreSQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pg_role_drop, this is the rule to start with:
pg_role_drop is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_role_drop call is checked against it from then on.
Questions about pg_role_drop
Drop a PostgreSQL role. Use ifExists (default: true) to skip gracefully if the role does not exist. 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 pg_role_drop: 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.
pg_role_drop 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 pg_role_drop 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 pg_role_drop. 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.
pg_role_drop is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PostgreSQL MCP Server, and thousands of servers like it.
Across the catalogue