pg_transaction_savepoint
Create a savepoint within a transaction for partial rollback.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-transaction-savepoint.md
What pg_transaction_savepoint does on PostgreSQL MCP Server
AI agents use pg_transaction_savepoint to create or update resources in PostgreSQL MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PostgreSQL MCP Server environment.
Why pg_transaction_savepoint is rated Medium
The tool creates a savepoint, which is a reversible write operation that modifies the transaction state. It does not execute arbitrary queries, delete data irreversibly, or move money. While savepoints themselves are benign transaction control constructs, their misuse in an agentic context could cause unintended transaction behavior or state management issues.
From the tool's definition Tool description states 'Create a savepoint within a transaction for partial rollback.' Savepoints are transaction control mechanisms that modify database transaction state by creating rollback points.
Attacks that exploit this kind of access
The rule that runs pg_transaction_savepoint 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_savepoint, this is the rule to start with:
pg_transaction_savepoint stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_transaction_savepoint call is checked against it from then on.
Questions about pg_transaction_savepoint
Create a savepoint within a transaction for partial rollback. It is categorised as a Write tool in the PostgreSQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_transaction_savepoint: 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.
pg_transaction_savepoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pg_transaction_savepoint 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.
Set action: deny in the PolicyLayer policy for pg_transaction_savepoint. 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.
pg_transaction_savepoint 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.
More on PostgreSQL MCP Server, and thousands of servers like it.
This server
Across the catalogue