This record as markdown: /tools/io-github-devopam-mcpg/partman-run-maintenance.md
What partman_run_maintenance does on Mcpg
AI agents invoke partman_run_maintenance to trigger actions in Mcpg. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why partman_run_maintenance is rated High
This tool appears to execute maintenance operations (likely partition management via pg_partman extension) that can modify database state and performance. While not immediately destructive or financial, it triggers external operations whose effects depend on the partition configuration and maintenance logic.
From the tool's definition Tool name 'partman_run_maintenance' suggests execution of maintenance operations on a PostgreSQL partitioning system. The 'run' verb combined with 'maintenance' indicates triggering of automated or scheduled operations.
Attacks that exploit this kind of access
The rule that runs partman_run_maintenance 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 partman_run_maintenance, this is the rule to start with:
partman_run_maintenance stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 partman_run_maintenance call is checked against it from then on.
Questions about partman_run_maintenance
partman_run_maintenance is a execute tool on the Mcpg MCP server. It is categorised as a Execute tool in the Mcpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcpg MCP server in PolicyLayer and add a rule for partman_run_maintenance: 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.
partman_run_maintenance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the partman_run_maintenance 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 partman_run_maintenance. 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.
partman_run_maintenance 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