pg_role_list
List PostgreSQL roles with attributes (login, superuser, createdb, etc.) and optional name filtering.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-role-list.md
What pg_role_list does on PostgreSQL MCP Server
AI agents call pg_role_list to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pg_role_list is rated Low
This tool retrieves and displays existing PostgreSQL role information without modifying, deleting, or executing any operations. It is a read-only query operation with minimal blast radius—the worst outcome is unauthorized disclosure of role metadata, which is typically non-sensitive administrative information. Low severity reflects the informational nature of the output.
From the tool's definition Tool name 'pg_role_list' and description 'List PostgreSQL roles with attributes' indicate a query/retrieval operation with 'optional name filtering' for search purposes. No create, modify, delete, or execute capabilities mentioned.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs pg_role_list 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_list, this is the rule to start with:
pg_role_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_role_list call is checked against it from then on.
Questions about pg_role_list
List PostgreSQL roles with attributes (login, superuser, createdb, etc.) and optional name filtering. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_role_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pg_role_list 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_list. 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_list 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.
This server
Across the catalogue