psql-list-databases

Lists all PostgreSQL databases via psql with owner, encoding, and size info.

SERVERGit SOURCEDave-London/Pare

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-git/psql-list-databases.md

WHAT IT DOES

What psql-list-databases does on Git

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

RISK

Why psql-list-databases is rated Low

This tool queries PostgreSQL system catalogs to retrieve informational metadata (database names, owners, encoding, sizes). It performs no writes, modifications, deletions, or code execution. The blast radius of misuse is minimal: an attacker could discover which databases exist and their properties, but cannot alter data or infrastructure. This is a straightforward Read operation.

From the tool's definition Tool description states it 'Lists all PostgreSQL databases' — a query operation that retrieves metadata without modification or deletion. The verb 'lists' and the read-only nature of querying database properties confirm no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs psql-list-databases safely

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

psql-list-databases Allowed

psql-list-databases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "psql-list-databases": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every psql-list-databases call is checked against it from then on.

FAQ

Questions about psql-list-databases

What does the psql-list-databases tool do? +

Lists all PostgreSQL databases via psql with owner, encoding, and size info. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on psql-list-databases? +

Register the Git MCP server in PolicyLayer and add a rule for psql-list-databases: 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 Git. Nothing to install.

What risk level is psql-list-databases? +

psql-list-databases is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit psql-list-databases? +

Yes. Add a rate_limit block to the psql-list-databases 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.

How do I block psql-list-databases completely? +

Set action: deny in the PolicyLayer policy for psql-list-databases. 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.

What MCP server provides psql-list-databases? +

psql-list-databases is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →