Detailed analysis of replication lag across all replicas.
AI agents call check_replication_lag_details 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.
The tool performs monitoring and diagnostics of replication status by querying PostgreSQL system tables and metrics. It retrieves information about lag across replicas without modifying database state, executing commands, or causing side effects. This is a diagnostic read operation consistent with the server's stated purpose of 'monitor, and optimize PostgreSQL databases.'
From the tool's definition Tool name and description indicate retrieval and analysis of replication lag metrics: 'Detailed analysis of replication lag across all replicas.' No modification, deletion, execution of arbitrary code, or financial operations are implied.
Documented attack patterns abuse exactly the kind of access check_replication_lag_details 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 check_replication_lag_details:
{
"version": "1",
"default": "deny",
"tools": {
"check_replication_lag_details": {}
}
}check_replication_lag_details 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.
Detailed analysis of replication lag across all replicas. 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 check_replication_lag_details: 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.
check_replication_lag_details 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 check_replication_lag_details 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 check_replication_lag_details. 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.
check_replication_lag_details 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.