// MCP TOOL REFERENCE

POSTGRES SCOUT TOOLS

38 tools from the Postgres Scout MCP Server, categorised by risk level.

View the Postgres Scout policy → Token cost: 5,177 tokens →

// ALL 38 POSTGRES SCOUT TOOLS

READ 30 tools

Read analyzeForeignKeys Analyze foreign key health and performance Read analyzeLocks Analyze current locks and blocking queries Read analyzeTableBloat Detect table and index bloat for VACUUM planning Read analyzeTimeSeries Advanced time-series analysis with window functions and anomaly detection Read analyzeTypeConsistency Analyze if text columns contain consistent data types Read checkConstraintViolations Check for rows that would violate a constraint before adding it Read describeTable Get comprehensive table information including columns, constraints, and indexes Read detectAnomalies Detect anomalies in query performance, connections, and data patterns Read detectSeasonality Detect seasonal patterns in time-series data Read explainQuery Analyze query performance using EXPLAIN (ANALYZE disabled) Read exploreRelationships Follow foreign key relationships to explore related records Read findDuplicates Find duplicate rows based on column combinations Read findMissingValues Find NULL values or missing data in columns Read findOrphans Find orphaned records with invalid foreign key references Read findRecent Find rows within a time window Read getCurrentActivity Get current active queries and connections Read getDatabaseStats Get comprehensive database statistics including size, cache hit ratio, and connection info Read getHealthScore Calculate overall database health score with component breakdown Read getHottestTables Identify tables with highest activity during a sample period Read getIndexUsage Analyze index usage and identify unused indexes Read getLiveMetrics Collect real-time database metrics over a time period with configurable intervals Read getSlowQueries Analyze slow queries from pg_stat_statements extension Read getTableMetrics Get comprehensive metrics for a specific table including I/O, scans, and maintenance stats Read listDatabases List all databases the user has access to Read listSchemas List all schemas in the current database Read listTables List all tables in a schema with size and statistics Read optimizeQuery Analyze a specific query and provide optimization recommendations (estimated plan only — ANALYZE unavailable) Read suggestIndexes Analyze query patterns and table scans to recommend missing indexes Read suggestPartitioning Analyze large tables and recommend partitioning strategies Read suggestVacuum Analyze and recommend VACUUM operations based on dead tuples and bloat

WRITE 5 tools

Write exportTable Export table data to various formats (CSV, JSON, SQL) Write generateInsertStatements Generate INSERT statements for data migration Write previewUpdate Preview which rows would be affected by an UPDATE without modifying data Write safeInsert Execute INSERT with safety guards: dry-run mode, maxRows limit, parameterized values, row batching, ON CONF... Write safeUpdate Execute UPDATE with safety guards: dry-run mode, maxRows limit, empty WHERE protection

DESTRUCTIVE 2 tools

Destructive previewDelete Preview which rows would be deleted without actually deleting them Destructive safeDelete Execute DELETE with safety guards: dry-run mode, maxRows limit, empty WHERE protection

EXECUTE 1 tools

Execute executeQuery Execute SELECT queries (read-only)

// RUNNING THIS SERVER

The managed route: connect Postgres Scout through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y postgres-scout-mcp

// FAQ

How many tools does the Postgres Scout MCP server have? +

The Postgres Scout MCP server exposes 38 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Postgres Scout tools? +

Route the Postgres Scout server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Postgres Scout tools fall into? +

Postgres Scout tools are categorised as Read (30), Write (5), Destructive (2), Execute (1). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.