pg_partman_check_default
Check if any data exists in the default partition that should be moved to child partitions. Data in default indicates partitions may be missing for certain time/value ranges.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-partman-check-default.md
What pg_partman_check_default does on PostgreSQL MCP Server
AI agents call pg_partman_check_default to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pg_partman_check_default is rated Low
This tool queries the state of PostgreSQL partitions to identify data in the default partition that should be redistributed. It is purely diagnostic—it retrieves and reports information without creating, modifying, or deleting any data. The read-only nature and low blast radius (informational only) justify the 'Read' category and 'low' severity.
From the tool's definition Tool description states it 'Check[s] if any data exists' - a read-only inspection operation that reports status without modifying data. No keywords indicating write, delete, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs pg_partman_check_default 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_partman_check_default, this is the rule to start with:
pg_partman_check_default 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 PostgreSQL MCP Server, apply this rule, and every pg_partman_check_default call is checked against it from then on.
Questions about pg_partman_check_default
Check if any data exists in the default partition that should be moved to child partitions. Data in default indicates partitions may be missing for certain time/value ranges. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_partman_check_default: 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.
pg_partman_check_default 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 pg_partman_check_default 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 pg_partman_check_default. 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.
pg_partman_check_default 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.
More on PostgreSQL MCP Server, and thousands of servers like it.
This server
Across the catalogue