There is an unknown number of corners that changes per path so we couldn't store them in individual predefined variables. It requires an array to store the corners so thats probably the reason this wasn't exposed as an action, there are a lot of use cases for this and it would be hard to cover without having a proxy to handle the array for whatever you are doing with the data.
For instance if we draw a line for you between the corners which is the easiest thing to do inside the action code to keep the array out of your hair.. The next request will be for control options for the line, and so on from there. Not really an effective solution. If we just output an Array of the points you can do whatever you want with that information and your own line implementation. But there is not an FsmArray variable in 1.7...
In 1.8 there are native arrays, so this would be something we could create an action for to have native support after its released, otherwise you would require ArrayMaker and a custom action to get the corners from the path for ArrayMaker.
