To generalise the issue, we need to look at why the policy was set.

Was it set to make money for the tow company, or was it set so that visitors could feel welcome.

It is easy to treat the outcome of a policy as more important than the reason for the policy. In this case the two hour limit would hopefully deter staff working in the building from using visitor spaces, but would not guarantee that a visitor space would always be available as more visitors may arrive than spaces reserved.

We often see similar things within the SQL Server world... "It is company policy that the data and log files must exist on separate drives so I need to move the log files of master, resource, model and msdb" - hardly a month goes by without a new thread opened on this topic.

Policy exists to help decision-making within the situation for which the policy was set. Unless we consider ourselves on a par with Vogons we should consider if the current situation is one where the policy should apply or if a different decision might give a better conclusion.

This does not give a mandate for anything goes - on top of all detailed policies there will be governance policies to give a framework for decision making. Exceptions to a policy should not be made by one person, but confirmed according to the governance framework (often this means get your boss to agree), and sometimes the exception will be so much better than the policy process that a new policy is needed.