security – Keystonejs, stop graphql to write the error and hints out

In the name of God.
Hi. I am developing a JAMStack project using keystonejs 6 and nuxtjs. As we know, keystonejs uses prisma and graphql (I guess apollo) to serve CRUD (generic) actions on our data model. So it makes the apis (even graphql or rest) and the errors generated are also generated by keystonejs. Now the problem is when the client send a wrong request to keystonjs, then it will help the client to correct the query and gives hints on it. For example if I query the next request:

await fetch("https://host:port/api/graphql", {
    "credentials": "include",
    "headers": {
        "User-Agent": "Mozilla/5.0 (X11; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0",
        "Accept": "*/*",
        "Accept-Language": "en-US,en;q=0.5",
        "Content-Type": "application/json",
        "Sec-Fetch-Dest": "empty",
        "Sec-Fetch-Mode": "cors",
        "Sec-Fetch-Site": "same-site"
    "referrer": "https://host:port/",
    "body": "{"operationName":null,"variables":{},"query":"{\n  navigationMenus(where: {status: {not: {equals: \"invisible\"}}}) {\n    ida\n    title\n    pageURL\n    childrenCount\n    parent {\n      id\n      pageURL\n      __typename\n    }\n    __typename\n  }\n}\n"}",
    "method": "POST",
    "mode": "cors"

as the field ida is not valid, is returns a bad request error with status code 400 (which is ok) and also helps the client with the following response:

errors  [ {…} ]
0   Object { message: "Cannot query field "ida" on type "NavigationMenu". Did you mean "id"?", locations: […], extensions: {…} }
message "Cannot query field "ida" on type "NavigationMenu". Did you mean "id"?"
locations   [ {…} ]
0   Object { line: 3, column: 5 }
line    3
column  5
extensions  Object { code: "GRAPHQL_VALIDATION_FAILED" }

So this will lead to some vulnerabilities since if I forget to make currect access controls on some fields, attacker may find field names with some tries and access to those data.
Although I can understand that this is not a very big issue, but is there a way to turn graphql hints off on production?

Read more here: Source link