pg_transaction_status

Check the status of an active transaction without modifying it.

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-transaction-status.md

WHAT IT DOES

What pg_transaction_status does on PostgreSQL MCP Server

AI agents call pg_transaction_status 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_transaction_status is rated Low

This tool only queries and retrieves the status of an existing transaction. It performs no modifications, deletions, code execution, or financial operations. The explicit statement that it does not modify data places it firmly in the Read category with low severity, as an AI agent checking transaction status poses minimal risk.

From the tool's definition Tool description states 'Check the status of an active transaction without modifying it' — explicitly a read-only operation with 'without modifying' confirming no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_transaction_status Allowed

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

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

FAQ

Questions about pg_transaction_status

What does the pg_transaction_status tool do? +

Check the status of an active transaction without modifying it. 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_transaction_status? +

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

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

Can I rate-limit pg_transaction_status? +

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

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

pg_transaction_status 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_transaction_status does on PostgreSQL MCP Server

Why pg_transaction_status is rated Low

The rule that runs pg_transaction_status safely

Questions about pg_transaction_status

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