replication_delete
Delete a replication task (destructive — requires confirm)
This record as markdown: /tools/nasbridge/replication-delete.md
What replication_delete does on Nasbridge
AI agents call replication_delete to permanently remove resources in Nasbridge, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why replication_delete is rated Critical
This tool permanently deletes a replication task, which is an irreversible action that cannot be undone. Deletion of replication configurations could break data synchronization workflows and cause data loss or inconsistency if not managed carefully. Although a confirmation is required as a safety measure, the underlying operation is destructive in nature.
From the tool's definition Tool name is 'replication_delete' and description states 'Delete a replication task (destructive — requires confirm)'. The word 'destructive' explicitly appears in the description, and delete operations are irreversible.
Attacks that exploit this kind of access
The rule that runs replication_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For replication_delete, this is the rule to start with:
replication_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every replication_delete call is checked against it from then on.
Questions about replication_delete
Delete a replication task (destructive — requires confirm). It is categorised as a Destructive tool in the Nasbridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nasbridge MCP server in PolicyLayer and add a rule for replication_delete: 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 Nasbridge. Nothing to install.
replication_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the replication_delete 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 replication_delete. 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.
replication_delete is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
Across the catalogue