pg_create_backup_plan
Generate a backup strategy recommendation with cron schedule.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-create-backup-plan.md
What pg_create_backup_plan does on PostgreSQL MCP Server
AI agents use pg_create_backup_plan to create or update resources in PostgreSQL MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PostgreSQL MCP Server environment.
Why pg_create_backup_plan is rated Medium
This tool creates or modifies backup scheduling configuration, which is a reversible data modification. It does not execute backups themselves (which would be Execute), nor does it delete data (Destructive). While it affects system operations, the core action is writing/creating a backup plan document or configuration entry.
From the tool's definition The tool description states it will 'Generate a backup strategy recommendation with cron schedule.' The verb 'Generate' indicates creation of new data (a backup plan), and 'cron schedule' suggests writing scheduling configuration to the system.
Attacks that exploit this kind of access
The rule that runs pg_create_backup_plan 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_create_backup_plan, this is the rule to start with:
pg_create_backup_plan stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create_backup_plan call is checked against it from then on.
Questions about pg_create_backup_plan
Generate a backup strategy recommendation with cron schedule. It is categorised as a Write tool in the PostgreSQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_create_backup_plan: 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_create_backup_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pg_create_backup_plan 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_create_backup_plan. 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_create_backup_plan 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