graphql-and-hidden-parameters

Probes GraphQL schemas to identify hidden parameters and authorization gaps.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/lNwNl/Methodos --skill graphql-and-hidden-parameters-lnwnl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphql-and-hidden-parameters
Source: https://github.com/lNwNl/Methodos/tree/main/docker/opencode/skills/graphql-and-hidden-parameters
Command: npx skills add https://github.com/lNwNl/Methodos --skill graphql-and-hidden-parameters-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GraphQL APIs often expose incomplete schemas publicly, restrict introspection, or accept undocumented parameters that can reveal authorization gaps and hidden functionality.

Core Features & Use Cases

  • Schema-first discovery: Start with introspection probes to map available types, fields, and capabilities even when the endpoint partially supports discovery.
  • Hidden parameter and schema abuse: Identify undocumented fields, permissive input shapes, and “extra” request body attributes by leveraging type probes and error-based inference.
  • Authorization gap exploration: Test for IDOR-style issues, nested object authorization weaknesses, and role-dependent field exposure.
  • Use case: When a target shows only a minimal “user profile” view, use this playbook to enumerate schema-referenced fields, attempt hidden parameter variations, and surface fields that appear in the schema but are not properly protected.

Quick Start

Use graphql-and-hidden-parameters to probe schema introspection and hunt for hidden fields and authorization gaps in a GraphQL endpoint.

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 discover hidden GraphQL fields and parameters when introspection is restricted?

GraphQL hidden parameter testing uses targeted __type and __schema probes alongside error-based field inference to enumerate undocumented fields and schema-referenced inputs even with restricted introspection, revealing authorization gaps and hidden functionality.

What is error-based enumeration in GraphQL schema discovery?

Error-based enumeration in GraphQL infers hidden fields and permissive input shapes by analyzing server error responses to targeted probes, allowing you to map undocumented schema attributes and discover authorization weaknesses across related objects.

How to test GraphQL APIs for authorization gaps and IDOR vulnerabilities?

Test GraphQL authorization gaps by probing nested object authorization weaknesses and role-dependent field exposure using schema-first discovery, then route findings to dedicated follow-on skills for API exploitation workflows.

Can I use GraphQL batching to expose hidden schema fields and data exposure risks?

GraphQL batching effects can be combined with schema-driven inputs and type probes to identify data exposure risks, allowing you to abuse permissive input shapes and surface undocumented fields that lack proper authorization controls.

Does this GraphQL schema enumeration approach work with minimal public endpoints?

Yes, this approach works on minimal endpoints by executing introspection probes to map available types, then inferring hidden parameters from responses to enumerate schema-referenced fields not properly protected in restricted views.