delete_replication_job

Delete a replication job.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/delete-replication-job.md

What delete_replication_job does on Proxmox MCP Server

AI agents call delete_replication_job to permanently remove resources in Proxmox MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_replication_job is rated Critical

Replication jobs are critical infrastructure configurations that, once deleted, cannot be automatically recovered without administrative intervention or backups. Deletion is an irreversible operation that prevents data replication and could disrupt disaster recovery capabilities. This meets the Destructive category criteria as it permanently removes a configured system resource.

From the tool's definition Tool name is 'delete_replication_job' and description states 'Delete a replication job.' The verb 'delete' combined with the destructive action of removing a replication job configuration indicates irreversible removal of data/configuration.

Questions about delete_replication_job

What does the delete_replication_job tool do? +

Delete a replication job. It is categorised as a Destructive tool in the Proxmox MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_replication_job? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for delete_replication_job: 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 Proxmox MCP Server. Nothing to install.

What risk level is delete_replication_job? +

delete_replication_job is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_replication_job? +

Yes. Add a rate_limit block to the delete_replication_job 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.

How do I block delete_replication_job completely? +

Set action: deny in the PolicyLayer policy for delete_replication_job. 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.

What MCP server provides delete_replication_job? +

delete_replication_job is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Proxmox MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Proxmox MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.