pg_locks

View current lock information.

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-locks.md

WHAT IT DOES

What pg_locks does on PostgreSQL MCP Server

AI agents call pg_locks 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_locks is rated Low

This tool queries the current state of locks in the PostgreSQL database (likely from pg_locks system view) and presents the information to the user. There are no mutations, deletions, code execution, or financial implications. It is a pure information retrieval operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'pg_locks' with description 'View current lock information' indicates a read-only operation that retrieves and displays lock status without modifying any data or triggering side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_locks 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_locks, this is the rule to start with:

pg_locks Allowed

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

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_locks call is checked against it from then on.

FAQ

Questions about pg_locks

What does the pg_locks tool do? +

View current lock information. 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_locks? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_locks: 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_locks? +

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

Can I rate-limit pg_locks? +

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

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

pg_locks 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_locks does on PostgreSQL MCP Server

Why pg_locks is rated Low

The rule that runs pg_locks safely

Questions about pg_locks

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