List logical replication slots with current lag in bytes and status.
AI agents call PostgreSQL_logical_replication_slot_lag to retrieve information from Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries replication slot metadata and lag metrics. It retrieves information about the state of logical replication slots but does not create, modify, delete, or execute operations. The action is purely informational/diagnostic, consistent with monitoring and observability use cases. No side effects, no data changes, no code execution.
From the tool's definition Tool name and description indicate 'List logical replication slots with current lag in bytes and status' — a read-only query operation that retrieves monitoring data without modification or execution of arbitrary code.
Documented attack patterns abuse exactly the kind of access PostgreSQL_logical_replication_slot_lag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres, and nothing reaches the server without passing your rules. This is the rule we recommend for PostgreSQL_logical_replication_slot_lag:
{
"version": "1",
"default": "deny",
"tools": {
"PostgreSQL_logical_replication_slot_lag": {}
}
}PostgreSQL_logical_replication_slot_lag is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List logical replication slots with current lag in bytes and status. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP server in PolicyLayer and add a rule for PostgreSQL_logical_replication_slot_lag: 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 Postgres. Nothing to install.
PostgreSQL_logical_replication_slot_lag is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the PostgreSQL_logical_replication_slot_lag 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 PostgreSQL_logical_replication_slot_lag. 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.
PostgreSQL_logical_replication_slot_lag is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
239 Postgres tools catalogued and risk-classified — across an index of 43,000+ MCP servers.