I appreciate the reasoning behind this - but perhaps the implementation could have been done in a more addin friendly way. this solution is more like using a stick of dynamite to catch a sardine.. 8)..
I'm not sure what options were discussed there (and what were not implemented due to time/budget issues) - but a few alternatives that would have been nicer -
1) Use the 'Program Library Options' settings to allow the user to enable/disable use of this button (you already have an option 'Hide Security Warnings' - so this is a small step further).
2) Show a warning dialog the first time the addin tries to handle this button - which allows the user to decide on a 'per addin' basis on whether to allow/deny permission to use this button. This would also include an 'always allow' checkbox so this could be remembered for future use. The dialog could also state that it 'could' be a security risk etc - and lets the user decide.
3) Provide some sort of callback function which allows the user to supply a list of Context menu buttons (similar to how buttons are supplied for the showmcedialog function). With this solution you could ensure the security info button was placed as the top (or default) menu option.
Option 2 would probably be my preference.. (as it caters for power users - and beginners who might not be able to find/understand the program settings menu).