If you do the following connection [Button->AND_Gate->Rail] it will activate/change/undock the Rail, depending on what you're trying to do (e.g next to a rotator for a single rotation).
As the AND_Gate has only 1 input, it's quite logic.
But if you have more than 1 input to the AND_Gate, the Rail will activate/change/undock even if only 1 input is active while the AND_Gate does not (as we deduce from the color staying orange).
Which is non-logical for an AND_Gate.

The picture shows the issue.
Only the AND_Gate is connected to the Rotator and only one activator is ON while the other is OFF so the gate is OFF as well.
But it still activates the Rotator.

You can't still bypass the problem by adding another gate between the Rail and the AND_gate.
The new gate having only on input, you don't have to care about the issue but still non-logical for an AND gate to do so.

Additional info provided by tester:

AND, OR, and the Toggle will all change the state of a rail they are connected to even if the state of the block itself does not change. (Not also changes on low instead of when it gets a low signal turning it high)