enable_logical_replication_on_demand
A execute tool on the Mcpg MCP server.
This record as markdown: /tools/io-github-devopam-mcpg/enable-logical-replication-on-demand.md
What enable_logical_replication_on_demand does on Mcpg
AI agents invoke enable_logical_replication_on_demand 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 enable_logical_replication_on_demand is rated High
The tool name strongly implies it enables logical replication on a PostgreSQL server, which is a significant server-level operation that triggers external replication processes and modifies PostgreSQL configuration (e.g., wal_level, replication slots). This is an Execute-level action with high blast radius as it affects the entire database replication topology.
From the tool's definition Tool name: 'enable_logical_replication_on_demand'. Description is empty/uninformative.
Attacks that exploit this kind of access
The rule that runs enable_logical_replication_on_demand 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 enable_logical_replication_on_demand, this is the rule to start with:
enable_logical_replication_on_demand 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 enable_logical_replication_on_demand call is checked against it from then on.
Questions about enable_logical_replication_on_demand
enable_logical_replication_on_demand 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 enable_logical_replication_on_demand: 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.
enable_logical_replication_on_demand 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 enable_logical_replication_on_demand 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 enable_logical_replication_on_demand. 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.
enable_logical_replication_on_demand 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