The administrative :command:`show` command provides a number of
useful inspection tools. Here's an example testing with the
-:command:`show result` subcommand from an active session with a
+:command:`evaluate` debug command from an active session with a
couple of avatars awake, comparing with the output from related
:command:`show group` and :command:`show element` invocations::
actor.avatar_admin_0
actor.avatar_luser0_0
- > show result actor.universe.groups['actor'].keys()
+ > evaluate actor.universe.groups['actor'].keys()
dict_keys(['avatar_admin_0', 'avatar_luser0_0'])
location: area.0,0,0
name: Keyo
- > show result actor.universe.contents['actor.avatar_luser0_0'].get('name')
+ > evaluate actor.universe.contents['actor.avatar_luser0_0'].get('name')
'Keyo'
-Note that for safety the :command:`show result` executes within the context of
-a command handler with only Python's :code:`__builtins__`, the :code:`mudpy`
-library package, and the active :code:`universe` available.
+Note that for safety the :command:`evaluate` executes within the context of
+a command handler with limited Python :code:`__builtins__`, the
+:code:`mudpy` library package, and the active :code:`universe` available,
+and also blocks evaluation of any statement containing double-underscores
+(:code:`__`) as well as :code:`lambda` functions. For admins to gain access
+to unsafe debugging commands, the ``.mudpy.limit.debug`` option must be
+enabled in configuration first and the service reloaded or restarted. It
+should still be considered unsafe, since the engine's file handling
+functions could easily alter accessible files or expressions like
+``9**9**9`` could be used to hang the service for indeterminate periods.