Skip to content
Skills Library
Security · Review & audit

graphql-security

/graphql-security

Secure GraphQL API deployments against introspection leaks, deep query abuse, and authorization bypass. Use when building, reviewing, or auditing GraphQL schemas, resolvers, or gateway configurations.

Licence
Apache-2.0
Last repository change
15.07.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
7
Deprecation

No signals detected. Repository changed on 15.07.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Secure GraphQL API deployments against introspection leaks, deep query abuse, and authorization bypass. Use when building, reviewing, or auditing GraphQL schemas, resolvers, or gateway configurations.

Original author description

Secure GraphQL API deployments against introspection leaks, deep query abuse, and authorization bypass. Use when building, reviewing, or auditing GraphQL schemas, resolvers, or gateway configurations.

How it works

  1. Authorization
  2. Disable Introspection
  3. Depth Limiting
  4. Query Cost Analysis
  5. Rate Limiting
  6. Implementation Checklist
  7. References
Original SKILL.md headings · 65 lines, 408 words
SKILL.md preview
---
name: graphql-security
description: >
  Secure GraphQL API deployments against introspection leaks, deep query
  abuse, and authorization bypass. Use when building, reviewing, or auditing
  GraphQL schemas, resolvers, or gateway configurations.
category: "secure_development"
subcategory: "web-security"
---

# GraphQL Security

GraphQL APIs introduce a threat surface distinct from REST. The flexible query language enables clients to request arbitrary data shapes, which can be abused for data exfiltration, denial of service, and authorization bypass if not constrained.

## Authorization

Authorization logic MUST live in the business-logic layer, not in individual resolvers.

Scattering authorization checks across resolvers creates gaps as the schema grows. Any resolver that forgets a check becomes an exploitable authorization flaw.

- Implement a single authorization layer beneath the GraphQL API
- Resolvers should delegate to this layer for every data access decision
- Apply the same authorization rules regardless of which query or mutation is used to reach the data
- See [GraphQL.org authorization guidance](https://graphql.org/learn/authorization/)

## Disable Introspection

GraphQL introspection exposes your full schema, including types, queries, mutations, and subscriptions. This is valuable for attackers mapping your attack surface.

- Disable introspection in staging and production environments
- Use the [graphql-disable-introspection](https://github.com/helfer/graphql-disable-introspection) plugin or equivalent validation rule
- Keep introspection enabled only in local development

## Depth Limiting

Deeply nested queries can trigger expensive recursive resolution, leading to resource exhaustion.

- Set a maximum query depth (typically 7-10 levels for most applications)
- Reject queries exceeding the depth limit before execution
- Use [graphql-depth-limit](https://github.com/stems/graphql-depth-limit) or equivalent

## Query Cost Analysis

Even within depth limits, queries can request expensive combinations of fields and connections.

- Assign a cost to each field and connection based on computational expense
- Set a maximum cost budget per query
- Reject queries exceeding the budget before execution
- Use [graphql-cost-analysis](https://github.com/pa-bru/graphql-cost-analysis) or equivalent

## Rate Limiting

GraphQL's single-endpoint design concentrates all operations on one URL, making rate limiting essential.

- Apply rate limits per client and per operation
- Use tighter limits on sensitive mutations (login, password reset, account creation)
- Use wider limits on read queries
- Use [graphql-rate-limit](https://github.com/teamplanes/graphql-rate-limit) or equivalent

## Implementation Checklist

- [ ] Authorization is enforced in the business-logic layer, not in resolvers
- [ ] Introspection is disabled in staging and production
- [ ] Query depth limit is configured and enforced
- [ ] Query cost analysis is enabled with per-field costs and a maximum budget
- [ ] Rate limiting is applied, with tighter limits on sensitive mutations
- [ ] Error messages do not leak schema details or internal structure
- [ ] Input validation is applied to all mutation arguments

## References

- [GraphQL.org best practices](https://graphql.org/learn/best-practices/)
- [OWASP GraphQL Security](https://owasp.org/www-chapter-vancouver/assets/presentations/2020-06_GraphQL_Security.pdf)

Versions

RepositoryScoreLicence
This page · redhatproductsecurity/prodsec-skills90Apache-2.0
thejefflarson/soundcheck90MIT

Database snapshot: 13.11.2026 · package version 84baa552e109 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95graphql-expert
    GraphQL API design and implementation. Use when building GraphQL APIs, designing schemas, implementing resolvers, or optimizing GraphQL performance.
  • 100building-graphql-server
    Build production-ready GraphQL servers with schema design, resolvers, and subscriptions. Use when building GraphQL APIs with schemas and resolvers. Trigger with phrases like "build GraphQL API", "create GraphQL server", or "setup GraphQL".
  • 100building-graphql-server
    Build production-ready GraphQL servers with schema design, resolvers, and subscriptions. Use when building GraphQL APIs with schemas and resolvers. Trigger with phrases like "build GraphQL API", "create GraphQL server", or "setup GraphQL".
  • 90api-security
    Design and enforce REST/GraphQL API Security paradigms. Use when: secure api, audit api security, implement jwt auth.
  • 100api-security
    API security across REST, GraphQL and gRPC, organised around the OWASP API Security Top 10:2023. USE WHEN: designing, implementing, or auditing REST, GraphQL, or gRPC APIs for security vulnerabilities DO NOT USE FOR: general API design patterns (use the `rest-api` / `graphql`…
  • 100secure-api-design
    Design secure REST, GraphQL, and RPC APIs. Use when adding endpoints or changing API contracts, authentication/authorization rules, or resource access policies.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.