A common use case for method contexts is filtering out accessors. In fact, A pre-defined context for that already exists. However, this context matches more methods than just trivial accessors (accessors with lazy initialisation and many others), since it just checks the method signature. A project may want non-trivial accessors test-covered, while filtering out the trivial ones.
This use case can be implemented by using maxComplexity / maxStatements and their aggregated version in ant, but not by maven plugin configuration itself.
There is an improvement request in Altassian's Clover Jira related to this: https://jira.atlassian.com/browse/CLOV-1173
However, I'd like to suggest for your consideration a slightly different approach that might be easier to implement: by using attributes for the new properties, the current implementation that takes the tag itself as name of the context can remain as is, and the backwards compatibility is preserved. eg:
<methodContexts> <trivialAccessors maxAggregatedStatements="1">(.* )?public .*(get|set|is)[A-Z].*</trivialAccessors> </methodContexts>