Changing API key permissions for an existing key does not update available tools

We cache the permissions available for a given key, so changing the permissions does not update the available tools.

This happens very infrequently, a potential solution would be to have a `reset-state` tool that resets the MCP server state for an API key completely. A downside to this is the LLM might overuse it when it's not called for.