"allow script to run" token

it's an idea that crossed my mind , as a game maker the problem i always encounter is that i can't control what script is used in my game, like , you can't check if someone use a shield to cheat in a shooting game, or if someone use a pushgun to wreck a ball game.

here is the idea:

a land owner can set, by hand or by script a "script token" wich is a bit like a password. Once set, it cannot be read nor by the owner or by script. It can only be set if you have the rights.

in a script you can use a function like "llSetscripttToken(string mytoken);" to define the script's token, ideally it should become a part of the script (only the script itself can change it's own token).

When the landowner untick the checkbox "allow outside scripts" he can tick a second checkbox "use script token"

at this moment, if a scripted object/attachment enter the parcel, its token is compared to the token set on the land, if it match, the script will be allowed to run, if it isn't, the script will be put to sleep, as "noscript" zones usually do.

it will allow game makers to restrict a parcel of land to only "trusted" scripts, this way every third party scripts will go to sleep, exepted the ones with the good token.

to allow the script to check the land token:

integer llCheckToken(vector position)
it will return TRUE, if the land has the same token as the script.
it will return false if the token is different.

to allow the script to set the land token:

integer llSetToken(string token); //will set the land token if PERMISSION_LAND_TOKEN is granted

(i repeat, the current token should NEVER be visible, so if you allow a script to set the token of your land, you cannot see the value that is set, however you can change it whenever you wish)

thanks for reading me!!
feel free to comment, i tried to find an idea simple to use, yet effective

Why shouldn't the owner be able to see the token for their own land? Can't you just do what is done for media URLs and have it blacked out for non-officer group members?
Other than that I like this idea.

well he can set it, but the field once set cannot be read, it would allow to "install" lets say a game zone without having to give the token to the land owner, the game server or setup script would do it for the land owner and the trust chain between the scripts would not be broken, of course he can overwrite the value at any time, by script or by hand, but he can't read a value that a script he allowed to change the token has set

*bump*

Eck, my post was lost in the forum downtime. Basically said in that event a list would be ideal, any tokens you add yourself, you can see (so you don't need to write them down or keep referring back to scripts you made).
Any tokens added by a script that you did not create can be seen in the list but not read (e.g it would give the object's name instead of the token), but can be blocked/removed from the list in order to disable all scripts running that token.

This way if you have say a security system running with a token, you can then install a vendor which uses a different token as an example.

*bump*