promote_read_replica
Promote a read replica to a standalone database.
This record as markdown: /tools/rsp2k-mcp-vultr/promote-read-replica.md
What promote_read_replica does on Vultr MCP
AI agents use promote_read_replica to create or update resources in Vultr MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vultr MCP environment.
Why promote_read_replica is rated Medium
Promoting a read replica to a standalone database changes the database topology and configuration. This is a Write/reconfiguration action that modifies infrastructure state. While potentially disruptive (it changes replication relationships and could affect application connectivity), it is not purely destructive as the data is preserved and the operation creates a new standalone instance.
From the tool's definition Promote a read replica to a standalone database
Attacks that exploit this kind of access
The rule that runs promote_read_replica safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For promote_read_replica, this is the rule to start with:
promote_read_replica 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 Vultr MCP, apply this rule, and every promote_read_replica call is checked against it from then on.
Questions about promote_read_replica
Promote a read replica to a standalone database. It is categorised as a Write tool in the Vultr MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vultr MCP server in PolicyLayer and add a rule for promote_read_replica: 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 Vultr MCP. Nothing to install.
promote_read_replica 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 promote_read_replica 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 promote_read_replica. 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.
promote_read_replica is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
This server
Across the catalogue