Custom disabling of specific tools

[bogzbonny]

Is there an easy workflow for disabling certain tools when the MCP server starts?

Currently the best way I've been able to figure this out is by manually implementing the ServerHandler for my server however it would be nice to just be able to use the #[tool_handler] macro and maybe add in my custom disable logic within the get_info function which needs to be manually implemented (just an idea).

Maybe I'm missing something and this is already possible. Thanks for the great work!

[4t145]

You can override the default implementation of get_info, so I don't get the question? If there's any member method cannot be overrided while using macros, please let me know.

[bogzbonny]

I guess all it comes down to is design flow of disabling tools. I found it to be a bit confusing at first, as I had to fully manually implement ServerHandler, wasn't a huge deal I had to dig around a bit to figure out what that would look like (expanded the tool_handler macro), there just could have been a bit better of a dev experience, maybe even just better documentation on how to use ServerHandler would have helped.

[alexhancock]

We have new docs that show ServerHandler being used in a number of contexts here https://github.com/modelcontextprotocol/rust-sdk/blob/main/docs/FEATURES.md

If there is a documentation update we could make to make it more clear, or even a PR as you say to make a great DX let us know @bogzbonny