Start reverse port forward
AI agents invoke execute_rportfwd_start 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.
Reverse port forwarding is a dynamic network operation that redirects traffic flows and enables unauthorized access to internal systems. While not destructive in the sense of deleting data, it represents active execution of a network operation whose effects depend on parameters (target ports, addresses) and can expose sensitive internal services.
From the tool's definition Tool enables 'Start reverse port forward' which establishes reverse port forwarding—a network redirection mechanism that allows external systems to connect back through the Cobalt Strike beacon to access internal services.
Attacks that exploit this kind of access
Start 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.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for execute_rportfwd_start: 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.
execute_rportfwd_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_rportfwd_start 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 execute_rportfwd_start. 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.
execute_rportfwd_start 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →