This record as markdown: /tools/io-github-devopam-mcpg/read-pg-stat-recovery.md
What read_pg_stat_recovery does on Mcpg
AI agents call read_pg_stat_recovery to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_pg_stat_recovery is rated Low
The naming convention strongly suggests this tool queries PostgreSQL recovery status information (pg_stat_recovery is a standard PostgreSQL system view). No modification, deletion, or execution of arbitrary operations is implied. It retrieves monitoring/diagnostic data with no side effects.
From the tool's definition Tool name 'read_pg_stat_recovery' contains 'read' and 'pg_stat' prefix, indicating retrieval of PostgreSQL recovery statistics. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
The rule that runs read_pg_stat_recovery safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_pg_stat_recovery, this is the rule to start with:
read_pg_stat_recovery is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every read_pg_stat_recovery call is checked against it from then on.
Questions about read_pg_stat_recovery
read_pg_stat_recovery is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for read_pg_stat_recovery: 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 Mcpg. Nothing to install.
read_pg_stat_recovery 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 read_pg_stat_recovery 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 read_pg_stat_recovery. 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.
read_pg_stat_recovery is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue