// MCP TOOL REFERENCE

AWS LABS POSTGRES MCP SERVER TOOLS

7 tools from the AWS Labs postgres MCP Server MCP Server, categorised by risk level.

View the AWS Labs postgres MCP Server policy →

READ TOOLS

get_database_connection_info Get all cached database connection information get_job_status get background job status get_table_schema Fetch table columns and comments from Postgres is_database_connected Check if a connection has been established

WRITE TOOLS

connect_to_database Connect to a specific database and save the connection internally create_cluster Create an Aurora Postgres cluster

EXECUTE TOOLS

run_query Run a SQL query against PostgreSQL

// FAQ

How many tools does the AWS Labs postgres MCP Server MCP server have? +

The AWS Labs postgres MCP Server MCP server exposes 7 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on AWS Labs postgres MCP Server tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the AWS Labs postgres MCP Server server.

What risk categories do AWS Labs postgres MCP Server tools fall into? +

AWS Labs postgres MCP Server tools are categorised as Read (4), Write (2), Execute (1). Each category has a recommended default policy.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →