security-review-owasp-graphql

Review GraphQL schemas, resolvers, and configurations for authorization gaps and query abuse.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-graphql
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review-owasp-graphql
Source: https://github.com/sjinks/ai-owasp-skillset/tree/main/.github/skills/security-review-owasp-graphql
Command: npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-graphql

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you review GraphQL services for weaknesses that expose sensitive data or overload production systems, including resolver-level authorization gaps, expensive query shapes, batching abuse, and downstream injection paths.

Core Features & Use Cases

  • Schema and resolver review: Inspect queries, mutations, subscriptions, and field-level access control instead of relying only on top-level route authentication.
  • Abuse-path analysis: Evaluate depth, complexity, pagination, introspection, batching, and error handling for practical exploitation risk.
  • Evidence-based findings: Produce concrete security findings tied to code, configuration, tests, or observable behavior, with minimal remediation guidance.
  • Use case: A reviewer can assess a GraphQL API before release to confirm that sensitive fields are gated and that expensive queries cannot be abused.

Quick Start

Use the security-review-owasp-graphql skill to review the selected GraphQL schema, resolvers, and production settings for authorization gaps, query abuse, and downstream injection risks.

Frequently Asked Questions about security-review-owasp-graphql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review GraphQL authorization gaps and query abuse risks?

Review GraphQL authorization gaps by inspecting field-level access control, resolver sinks, query complexity, batching, and introspection exposure against OWASP guidance. This produces evidence-based security findings tied to code or configuration without relying solely on top-level route authentication.

What is field-level access control in GraphQL security reviews?

Field-level access control in GraphQL security reviews ensures sensitive data exposure is prevented by gating individual fields within schemas, resolvers, mutations, and subscriptions, rather than trusting top-level route authentication to block unauthorized requests.

How do I prevent expensive GraphQL queries from overloading production?

Prevent expensive GraphQL queries from overloading production by analyzing query depth, complexity limits, pagination, and batching abuse during a security review. This evaluates practical exploitation risk and confirms production configuration enforces query cost limits.

Does this security review check GraphQL introspection and error handling?

This security review checks GraphQL introspection exposure and error handling. It assesses whether introspection is disabled in production and evaluates error responses to prevent downstream injection risks and sensitive data leakage.

Can I assess GraphQL mutations and subscriptions for downstream injection risks?

You can assess GraphQL mutations and subscriptions for downstream injection risks. The review evaluates resolver sinks, input validation, and production configuration to identify vulnerable data paths and produce concrete security findings tied to observable behavior.

What are the limitations of reviewing GraphQL schemas without checking resolvers?

Reviewing GraphQL schemas without checking resolvers limits abuse-path analysis. You must evaluate resolver sinks, query cost limits, and error handling directly against code and configuration to detect downstream injection risks and confirm sensitive fields are actually gated.