{"agent":"claude","input":"A GitHub issue labelled security says this GraphQL server accepts queries of any depth. Read package.json, handler/graphql.mjs, netlify.toml, src/schema/index.js, src/schema/connections.js, src/schema/apiHelper.js and the specs under src/schema/__tests__ first. Trust package.json scripts over the README where they disagree, and say where they disagree. In the pull request, show one cycle in the schema with the field names that form it, and say whether the connection resolvers load a whole relation before slicing it. Add a validation rule that limits query depth, counting through fragment spreads. Either add graphql-depth-limit, after checking it supports the pinned graphql version, or write the rule against that version's visitor API; say which and why. Put the rule under src so the build includes it, and pass it to createHandler as an array of validationRules so the standard rules still apply. Before choosing the limit, measure the depth of every query in the specs and of the standard introspection query that the GraphiQL page in public/index.html sends, list them, and set the default above the deepest; read the limit from an environment variable. Add Jest specs using validate: at the limit, one past it, deep through nested fragments, and introspection. Run npm install, then npm test, then start the server with npm run watch and post one ordinary and one too-deep query with curl; paste both status codes and bodies. State what a depth limit does not stop, such as many aliases of one wide field. Open a pull request that closes the issue.","resources":[{"url":"https://github.com/your-org/your-app"}]}