Prisma-Cloud policy filtering permissions output

[automate9000]

Using a Prisma-Cloud key to pull policies from the console and then filtering using "--policy-metadata-filter policy.label=TEST2,policy.label=TEST1" does not throw an error if the role assigned to the key doesn't include Policies/View permission. Instead everything executes and displays results as normal, although unfiltered. This is misleading for the end-user who assumes filtering has occurred..

[stale]

Thanks for contributing to Checkov! We've automatically marked this issue as stale to keep our issues list tidy, because it has not had any activity for 6 months. It will be closed in 14 days if no further activity occurs. Commenting on this issue will remove the stale tag. If you want to talk through the issue or help us understand the priority and context, feel free to add a comment or join us in the Checkov slack channel at codifiedsecurity.slack.com
Thanks!

[stale]

Closing issue due to inactivity. If you feel this is in error, please re-open, or reach out to the community via slack: codifiedsecurity.slack.com Thanks!