graphql-and-hidden-parameters

Probe GraphQL schemas for hidden fields and authorization gaps.

1.6k|204|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/yaklang/hack-skills --skill graphql-and-hidden-parameters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphql-and-hidden-parameters
Source: https://github.com/yaklang/hack-skills/tree/main/skills/graphql-and-hidden-parameters
Command: npx skills add https://github.com/yaklang/hack-skills --skill graphql-and-hidden-parameters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GraphQL exposure often leaks sensitive data through undocumented fields, weak auth checks, or lax schema configurations. This skill provides a structured approach to discover, test, and reason about hidden parameters and authorization gaps in GraphQL APIs.

Core Features & Use Cases

  • Introspection discovery: map the full schema to identify types, fields, and potential misconfigurations.
  • Hidden parameter testing: probe for undocumented fields, extra properties, and weak field-level access controls.
  • Batching and auth testing: assess how batched requests interact with authorization, rate limits, and data access across related objects.

Quick Start

Run a simple introspection query to enumerate types and fields, then probe for undocumented fields and authorization gaps.

Frequently Asked Questions about graphql-and-hidden-parameters

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

FAQPage Schema
How do I find undocumented fields and hidden parameters in a GraphQL API?

To find undocumented fields in a GraphQL API, you perform introspection queries to map the schema and probe for hidden fields. This process identifies types, fields, and weak field-level access controls.

What is GraphQL introspection and how does it expose schema vulnerabilities?

GraphQL introspection is a query mechanism that maps the full schema to identify types and fields. It exposes vulnerabilities by revealing undocumented fields, misconfigurations, and nested authorization gaps.

How do I test GraphQL batching for authorization gaps?

To test GraphQL batching for authorization gaps, you assess how batched requests interact with authorization and rate limits. This reveals data access issues across related objects within a single batch.

Can I enumerate a GraphQL schema when introspection is restricted?

When introspection is restricted, you can still probe for hidden fields and undocumented properties by guessing field names. This approach uncovers weak auth checks and lax schema configurations.

What is the best way to document GraphQL authorization gaps for remediation?

The best way to document GraphQL authorization gaps is by recording findings with reproducible steps and concrete payload examples. This guides remediation by demonstrating exactly how sensitive data leaks.