pg_migration_history

Query migration history with optional filtering by status and source system.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

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-neverinfamous-postgres-mcp/pg-migration-history.md

WHAT IT DOES

What pg_migration_history does on PostgreSQL MCP Server

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

RISK

Why pg_migration_history is rated Low

This tool retrieves historical data about migrations with no side effects. It performs a read-only query operation similar to a SELECT statement filtered by optional criteria. The action is informational only and does not modify, execute, or delete any data.

From the tool's definition Tool description states "Query migration history" which is a retrieval operation. The optional filtering parameters (status, source system) are query constraints, not write/execute/destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_migration_history safely

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

pg_migration_history Allowed

pg_migration_history 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": {
    "pg_migration_history": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_migration_history call is checked against it from then on.

FAQ

Questions about pg_migration_history

What does the pg_migration_history tool do? +

Query migration history with optional filtering by status and source system. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_migration_history? +

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

What risk level is pg_migration_history? +

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

Can I rate-limit pg_migration_history? +

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

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

pg_migration_history is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What pg_migration_history does on PostgreSQL MCP Server

Why pg_migration_history is rated Low

The rule that runs pg_migration_history safely

Questions about pg_migration_history

More on PostgreSQL MCP Server, and thousands of servers like it.