Due to a difficulty with creating LSL script tools for managing Estate Ban Lists and similar, I assume, it's not that easy to detect, if an owner of a script is an estate owner/manager, I suggest to create capabilities to have estate tools for scripted objects and off world tools. Those capabilities should work similar to RegAPI. The Estate Owner/Manager logs into an url like https://cap.secondlife.com/get_estate_capabilities and gets a list of functions that can be called. These should include modifying Access and Ban lists on either keys or names, whatever is possible. If it's keys, then there needs to be a capability to convert avatar/group names to keys. Also a capability to Allow/Disallow public access would be important to have automated means to counter griefing. Other estate capabilities useful would be to allow teleporting home one or all, turning on/off debug parameters. And one thing that could be really helpful is, to get a list of agents inside a region currently (once for automatic ban lists and for the other, to find those phased out griefers, that cannot be found by other means) and possibly a list of agents loggin in/out of simulators with time. Why I suggest using capabilities instead of LSL to manage Estate lists/parameters is, using capabilities it's easier to detect if the request was initiated by the estate owner/manager and afaik a sim only knows if an agent is estate owner or manager, if the agent is an agent currently connected to the sim.