Summary
Run a full GraphQL assessment from reconnaissance to exploit validation: identify the endpoint, enumerate the schema, trigger introspection abuse or schema oracles, test batching and depth limiting, verify authorization flaws, and confirm high-impact mutation abuse with evidence.- Fingerprints GraphQL endpoints and distinguishes server behavior from the error response alone
- Enumerates query, mutation, and subscription surfaces to reveal hidden operations and leaked object fields
- Tests GraphQL-specific DoS vectors such as depth, alias abuse, and batching that generic API testing misses
- Probes argument injection, mass assignment, IDOR, and field-level authorization issues through real mutation flows
- Produces a confirmed exploit chain only when the evidence supports it
SKILL.md file
Discover skill details
Discover skill details
GraphQL Raider
Test GraphQL endpoints as a high-risk API surface by moving from reconnaissance to exploit-chain validation without guessing.What Does It Check?
The skill covers the GraphQL-specific attack surface: introspection abuse, field suggestion oracles, depth and batching abuse, alias-based rate-limit bypass, arguments that can carry injection payloads, broken authorization on mutations, CSRF via GET-style mutations, and subscription or mass-assignment abuse.In scope:/graphqland common GraphQL endpoint variants- Introspection and schema enumeration
- Query depth, batching, alias, and rate-limit bypass checks
- Injection via arguments (SQLi, NoSQLi, SSTI)
- Broken object-level and field-level authorization
- CSRF via GET mutations and mutation abuse through GraphQL
- Subscription hijacking and mass assignment via mutation parameters
- WAF and protection bypass patterns
- Generic web app testing outside the GraphQL endpoint
- Full pentest reporting across a whole application; this skill targets the GraphQL surface specifically
How It Works
Phase 1 — Reconnaissance: Find & Fingerprint GraphQLCheck common GraphQL paths and send a minimal__typename request to confirm the endpoint and server type. Response signatures reveal whether introspection is enabled or if the server is exposing a particular framework behavior.Phase 2 — Schema EnumerationEnumerate the schema, list types, and prioritize mutation surfaces. The skill extracts the hidden objects, arguments, and sensitive fields most likely to produce privilege escalation or data leakage.Phase 3 — Attack SelectionMove through the highest-value GraphQL abuse classes in order: introspection abuse, field suggestion oracle, query depth attacks, batching, alias-based rate-limit bypass, injection through arguments, broken object-level auth, broken field-level auth, CSRF via GET mutations, circular fragment DoS, subscription hijacking, and mass assignment.Phase 4 — Confirm the ExploitOnly treat a finding as real if it is supported by a reproducible response or a working mutation. The skill validates privilege escalation or data access before writing up the result.Phase 5 — Report the FindingWrite a structured result with the endpoint affected, the root cause, the exploit path, relevant evidence, and a concrete remediation recommendation.Output
Known Limitations
- The skill requires a real target or a reproducible GraphQL payload to validate behavior
- Some protections depend on server-side API logic and may require account setup, multi-user testing, or WebSocket access
- It does not replace a full application pentest; it focuses on the GraphQL attack surface
Benchmark Results
Tested on claude-sonnet-4-6 via Claude Code CLI. Same prompt, same model, same target. The only variable is whether the skill is loaded.graphql-raider, the workflow covered the full GraphQL methodology in a single turn and produced a validated exploit chain with zero false positives.

