I may be wrong here, but I think it just means that someone can use the Command object to do bad things. That is, he should not be trusted if someone else is scripting him.
See script-safe in this article. Each instance that talks about this phrase on the Internet refers to it as if you were marking an ActiveX control saying: "This control does not perform I / O or only returns the server to the server from which it came", but the object Command does not. It can be used to accomplish many things that may be unsafe.
The “safe” they are talking about and the “safe” to prevent SQL injection are two different things. An article about using the ADO command object to parameterize your data is included. You have to do it.
And Microsoft confirms this here:
http://msdn.microsoft.com/en-us/library/ms676585(v=VS.85).aspx
source share