pg_terminate_backend

Terminate a database connection (forceful, use with caution).

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-terminate-backend.md

WHAT IT DOES

What pg_terminate_backend does on PostgreSQL MCP Server

AI agents use pg_terminate_backend 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.

RISK

Why pg_terminate_backend is rated Medium

An AI agent can call pg_terminate_backend faster than any human can review: one bad instruction and it creates or modifies resources in PostgreSQL MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_terminate_backend Rate-limited

pg_terminate_backend 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pg_terminate_backend": {
      "limits": [
        {
          "counter": "pg_terminate_backend_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about pg_terminate_backend

What does the pg_terminate_backend tool do? +

Terminate a database connection (forceful, use with caution). 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.

How do I enforce a policy on pg_terminate_backend? +

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

pg_terminate_backend is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pg_terminate_backend? +

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

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

pg_terminate_backend 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_terminate_backend does on PostgreSQL MCP Server

Why pg_terminate_backend is rated Medium

The rule that runs pg_terminate_backend safely

Questions about pg_terminate_backend

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