performing-graphql-introspection-attack

Extract GraphQL schemas and test for introspection and batching vulnerabilities.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Acczdy/MoZiSec --skill performing-graphql-introspection-attack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performing-graphql-introspection-attack
Source: https://github.com/Acczdy/MoZiSec/tree/main/api-security/.claude/skills/performing-graphql-introspection-attack
Command: npx skills add https://github.com/Acczdy/MoZiSec --skill performing-graphql-introspection-attack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Exposes whether a GraphQL endpoint leaks its full schema and identifies sensitive types, fields, queries, and mutations that increase attack surface. It helps testers discover introspection-enabled endpoints, detect schema reconstruction via error messages, and determine protections (depth/complexity limits, batching support, field-level authorization) to prevent data exposure and DoS.

Core Features & Use Cases

  • Full Schema Extraction: Runs standard introspection to retrieve queries, mutations, types, interfaces, enums, and directives when enabled.
  • Schema Reconstruction & Brute-Forcing: Uses error suggestions and field wordlists to discover schema elements when introspection is disabled.
  • Attack Simulations: Tests query depth, alias-based batching, wide/duplicate-field queries, circular fragments, and batched requests to evaluate DoS and rate-limit bypass vectors.
  • Sensitive Field Detection: Scans extracted schemas for common sensitive field patterns (password, token, secret, apiKey, etc.) and highlights risky mutations.
  • Use Case: Assess an e-commerce GraphQL API to find exposed admin mutations, user PII leaks, missing depth limits, and batching vulnerabilities that could enable credential brute-force or resource exhaustion.

Quick Start

Run the performing-graphql-introspection-attack skill against the target GraphQL endpoint with a valid authorization header to extract the schema and run depth, batch, and sensitive-field checks.

Frequently Asked Questions about performing-graphql-introspection-attack

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

FAQPage Schema
How do I extract a full GraphQL schema for security testing?

To extract a full GraphQL schema for security testing, run standard introspection queries against the endpoint to retrieve all queries, mutations, types, interfaces, enums, and directives when introspection is enabled.

Can I discover GraphQL schema fields when introspection is disabled?

You can discover GraphQL schema fields when introspection is disabled by using error suggestion messages and field wordlists to brute-force and reconstruct hidden schema elements.

What GraphQL query abuse vulnerabilities should I test for during penetration testing?

During GraphQL penetration testing, you should test for query depth limits, alias-based batching, wide and duplicate-field queries, circular fragments, and batched requests to evaluate denial of service and rate-limit bypass vectors.

Does this GraphQL security check require authenticated requests?

This GraphQL security check requires HTTP access to the endpoint and the ability to send authenticated requests with a valid authorization header when needed to extract the schema and run depth, batch, and sensitive-field checks.

How do I detect sensitive fields in an extracted GraphQL schema?

To detect sensitive fields in an extracted GraphQL schema, scan the schema for common sensitive patterns like password, token, secret, and apiKey, and highlight risky mutations that increase the attack surface.

Do I need Python and the requests library to run GraphQL introspection attacks?

You need a Python environment with the requests library to execute probes and scripts that perform GraphQL introspection attacks, apply schema extraction, and identify sensitive fields and potential vulnerabilities.