Low Risk

list_databases

List databases with owner, encoding, and size.

How to control list_databases ↓

What list_databases does on PostgreSQL SSH MCP Server

AI agents call list_databases to retrieve information from PostgreSQL SSH MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_databases needs a policy

This tool retrieves database information (owner, encoding, size) through a read-only query. It has no side effects—it does not create, modify, delete, or execute operations on the database. The action is purely informational enumeration, consistent with the 'Read' category pattern seen in sibling tools like 'list_schemas' and 'list_active_connections'.

From the tool's definition Tool name 'list_databases' and description 'List databases with owner, encoding, and size' indicate a query operation that retrieves metadata without modification.

Documented attack patterns abuse exactly the kind of access list_databases gives an agent:

How to control list_databases

PolicyLayer is an MCP gateway — it sits between your AI agents and PostgreSQL SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_databases:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_databases": {}
  }
}

list_databases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register PostgreSQL SSH MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_databases

What does the list_databases tool do? +

List databases with owner, encoding, and size. It is categorised as a Read tool in the PostgreSQL SSH MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_databases? +

Register the PostgreSQL SSH MCP Server MCP server in PolicyLayer and add a rule for 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 PostgreSQL SSH MCP Server. Nothing to install.

What risk level is list_databases? +

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

Can I rate-limit list_databases? +

Yes. Add a rate_limit block to the 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 list_databases completely? +

Set action: deny in the PolicyLayer policy for 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 list_databases? +

list_databases is provided by the PostgreSQL SSH MCP Server MCP server (zlash65/postgresql-ssh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PostgreSQL SSH MCP Server tool call.

Start from PostgreSQL SSH MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

12 PostgreSQL SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.