pg_show_settings
Show current PostgreSQL configuration settings. Filter by name pattern or exact setting name. Accepts: pattern, setting, or name parameter.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-show-settings.md
What pg_show_settings does on PostgreSQL MCP Server
AI agents call pg_show_settings 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_show_settings is rated Low
The tool performs read-only retrieval of PostgreSQL configuration settings. It accepts filter parameters (pattern, setting, name) to query and display existing configuration values. There are no side effects, no data modification, no code execution, and no irreversible operations. This is a straightforward informational query, placing it firmly in the Read category with low severity risk.
From the tool's definition Tool description states 'Show current PostgreSQL configuration settings' with filtering by name pattern or setting name. This is a query/retrieval operation with no data modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs pg_show_settings 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_show_settings, this is the rule to start with:
pg_show_settings 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_show_settings call is checked against it from then on.
Questions about pg_show_settings
Show current PostgreSQL configuration settings. Filter by name pattern or exact setting name. Accepts: pattern, setting, or name parameter. 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_show_settings: 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_show_settings 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_show_settings 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_show_settings. 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_show_settings 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