execute_rportfwd_stop · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_rportfwd_stop does on Cobalt Strike MCP Server

AI agents invoke execute_rportfwd_stop to trigger actions in Cobalt Strike MCP Server. 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 IT NEEDS A POLICY

Why execute_rportfwd_stop needs a policy

This tool executes a command that terminates an active reverse port forwarding tunnel on a compromised beacon. While not destructive to persistent data, it is an active operation that changes system state and network connectivity. It belongs in Execute rather than Read because it performs an action with real-world effects (terminating network tunnels), not merely querying information.

From the tool's definition Tool is part of Cobalt Strike MCP Server which provides "beacon control" operations. The tool name 'execute_rportfwd_stop' indicates execution of a reverse port forwarding termination command.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_rportfwd_stop Rate-limited

execute_rportfwd_stop 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_rportfwd_stop": {
      "limits": [
        {
          "counter": "execute_rportfwd_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cobalt Strike MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_rportfwd_stop

What does the execute_rportfwd_stop tool do? +

Stop reverse port forward. It is categorised as a Execute tool in the Cobalt Strike MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_rportfwd_stop? +

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

What risk level is execute_rportfwd_stop? +

execute_rportfwd_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_rportfwd_stop? +

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

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

execute_rportfwd_stop is provided by the Cobalt Strike MCP Server MCP server (mickeydb/cobalt-strike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.