remove deprecated method that was allowing everything

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | yes
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | 
| License       | MIT
| Doc PR        | 

Follow-up on #103 by @cbastienbaron - i prefer to do a BC break over leaving a basically non-functioning method in place that can lead to severe security issues.

I think the reason this method turned up again was a merge conflict between the workflow and delete actions and the refactoring to the new way to do security checks.