PostgreSQL_get_important_settings

What PostgreSQL_get_important_settings does on Postgres

AI agents call PostgreSQL_get_important_settings to retrieve information from Postgres without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why PostgreSQL_get_important_settings is rated Low

This tool retrieves and displays PostgreSQL configuration data with no side effects. It is a read-only operation that gathers diagnostic information about database settings. While exposure of certain configuration details (e.g., credentials, paths) could inform a subsequent attack, the tool itself performs no destructive, write, financial, or code execution action.

From the tool's definition Tool name and description indicate retrieval of configuration parameters: 'Get important PostgreSQL configuration parameters and their current values.' The action is purely informational—querying existing settings without modification, deletion, or execution…

The rule that runs PostgreSQL_get_important_settings safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Postgres, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For PostgreSQL_get_important_settings, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "PostgreSQL_get_important_settings": {}
  }
}

Questions about PostgreSQL_get_important_settings