read_pg_stat_lock

A read tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

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-devopam-mcpg/read-pg-stat-lock.md

WHAT IT DOES

What read_pg_stat_lock does on Mcpg

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

RISK

Why read_pg_stat_lock is rated Low

The tool name prefix 'read_' combined with 'pg_stat_lock' strongly suggests querying PostgreSQL's built-in lock statistics view. This is a non-destructive data retrieval operation with no side effects. No modifications are made to data or system state. While the description is empty, the naming convention and context (production PostgreSQL server) provide sufficient clarity.

From the tool's definition Tool name 'read_pg_stat_lock' indicates a read operation on PostgreSQL's pg_stat_locks system view, which queries lock statistics without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_pg_stat_lock safely

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

read_pg_stat_lock Allowed

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

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

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

FAQ

Questions about read_pg_stat_lock

What does the read_pg_stat_lock tool do? +

read_pg_stat_lock is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_pg_stat_lock? +

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

What risk level is read_pg_stat_lock? +

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

Can I rate-limit read_pg_stat_lock? +

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

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

read_pg_stat_lock is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →