execute_cancel_file_download

What execute_cancel_file_download does on Cobalt Strike MCP Server

AI agents invoke execute_cancel_file_download 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 execute_cancel_file_download is rated High

This tool executes a cancellation command on a remote beacon (compromised host) to interrupt an in-progress file transfer. While not destructive or write-heavy, it triggers external effects on a target system whose outcome depends on the current state of downloads on that beacon. This is characteristic of Execute-category tools.

From the tool's definition Tool named 'execute_cancel_file_download' with description 'Cancel file download' on a Cobalt Strike red team operations server. The 'execute_' prefix and context of beacon control operations indicate this triggers an action on a compromised system.

The rule that runs execute_cancel_file_download safely

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

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

Questions about execute_cancel_file_download