This is not a security issue. The bug tracker is not the best place to ask usage questions. 

For me those are great news. I'm leading a solution which needs this information and it should be awesome.
Please apologies for this, but are you sure about it? This request is exponsing in a json file all urls opened by the user plus some processes id information.
If you say yes, I'll give instruction to the developers to use this information as main part of our solution.

Kind regards.

> This request is exposing in a json file all urls opened by
> the user plus some processes id information.

Yes, Chrome exposes data about the tabs and URLs for accessibility purposes. This content isn't available to untrusted contexts (e.g. a website cannot query it, for instance).

> If you say yes, I'll give instruction to the developers 
> to use this information as main part of our solution.

Just because the data is available does not mean that you can necessarily rely upon it being available in this format at this URL indefinitely. Other mechanisms that expose such data (e.g. the Chrome Developer Tools protocol) may be more stable and appropriate for your needs.

Can you please elaborate on what you hope to do with this data, and how you plan to query it?

As per comment#5 requesting someone from dev team for further clarification. Also cc'ing  elawrence@ from comment#4. Please help in triaging this further.

Dear Sindhu, thank you for your time.
We also tried reading the "Custom Tab" file, but even if we could read it (it is blocked when Chrome is running) its format is "SSNS", a custom format (session_backend.cc), and even if we could decode it, Is it the standard way to accomplish this task? :/