Uhhh ... that's not quite right. If you're going to go to all the trouble of actually making a new package and a new file (cause, you might as well make these shareable!), then you'd probably also add a security function somewhere. I would envision something like:

package dispatch;

my %disallowed = (
    security => 1,
);
sub security
{
    # Handle security here, somehow, returning a boolean.
}

# Because we're overloading can(), we can easily make it play nicely w
+ith AUTOLOAD.
sub can
{
    my $proto = shift;
    my ($method) = @_;

    return '' if $disallowed{$method};
    UNIVERSAL::can($proto, $method);
}

#### Functions to dispatch to below here

---------------

if (dispatch->security( ... ) and my $method = dispatch->can( ... ))
{
    $method->(@args);
}
[download]

Now, to correct a misconception - without serious craziness of the Devel:: variety, you cannot access a lexically scoped variable outside its scope. Period, Do Not Pass Go, End Of Story. In other words, it's not an issue. This goes for packages or closures. (That's kinda why they're called "closures".)