Access Denied error message, errorCode 180 is not clear in UI.

I hit this error when upon querying a table using the UI.

[
{
"message":null.
"errorCode":180
}
]

This message was unclear to me what the issue really is. I went into the logs and realized the broker is sending these logs: INFO `[BaseBrokerRequestHandler] [jersey-server-managed-async-executor-1] Access denied for requestId 111`.
Upon seeing this log message, I realized that I have accidentally configured ACL on my broker. which is throwing an exception.
It could really help if there could be a clearer error message like access denied etc.

Start by tracing errorCode 180 from the UI query response to the broker's "Access denied" log message. The issue is complete when an ACL-related denial produces a clear access-denied message in the UI instead of a null message.

Written by the indexing model from the issue text.