adb_reverse_remove

Remove a reverse forward (device → host), or all reverse forwards. Use after testing to clean up.

SERVERDeepadb SOURCEdeepadb

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/io-github-fullread-deepadb/adb-reverse-remove.md

WHAT IT DOES

What adb_reverse_remove does on Deepadb

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

RISK

Why adb_reverse_remove is rated Critical

Removing network port forwarding rules is an irreversible deletion of configuration state. The tool explicitly removes (deletes) reverse forwards, and the 'or all reverse forwards' option amplifies blast radius. While the effect is network configuration rather than data, the action is non-reversible without reconfiguration, fitting Destructive better than Write.

From the tool's definition 'Remove a reverse forward (device → host), or all reverse forwards'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_reverse_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_reverse_remove, this is the rule to start with:

adb_reverse_remove Hidden

adb_reverse_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "adb_reverse_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_reverse_remove call is checked against it from then on.

FAQ

Questions about adb_reverse_remove

What does the adb_reverse_remove tool do? +

Remove a reverse forward (device → host), or all reverse forwards. Use after testing to clean up. It is categorised as a Destructive tool in the Deepadb 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 adb_reverse_remove? +

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

What risk level is adb_reverse_remove? +

adb_reverse_remove 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 adb_reverse_remove? +

Yes. Add a rate_limit block to the adb_reverse_remove 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 adb_reverse_remove completely? +

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

adb_reverse_remove is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →