New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

PostgreSQL_logical_replication_slot_lag

List logical replication slots with current lag in bytes and status.

SERVERPostgres SOURCEmukul975/postgres-mcp-server
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/mukul975-postgres-mcp-server/postgresql-logical-replication-slot-lag.md

What PostgreSQL_logical_replication_slot_lag does on Postgres

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

Why PostgreSQL_logical_replication_slot_lag is rated Low

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.

Questions about PostgreSQL_logical_replication_slot_lag

What does the PostgreSQL_logical_replication_slot_lag tool do? +

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.

How do I enforce a policy on PostgreSQL_logical_replication_slot_lag? +

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.

What risk level is PostgreSQL_logical_replication_slot_lag? +

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

Can I rate-limit PostgreSQL_logical_replication_slot_lag? +

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.

How do I block PostgreSQL_logical_replication_slot_lag completely? +

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.

What MCP server provides PostgreSQL_logical_replication_slot_lag? +

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.

More on Postgres, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Postgres's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.