Back to catalog
Static reviewDevelopment

Skill dossier

performing-graphql-introspection-attack

Source declaration

Performs GraphQL introspection attacks that extract the full API schema (types, queries, mutations, subscriptions, field definitions), map the attack surface, test query depth/complexity limits, and exploit GraphQL-specific weaknesses such as batching attacks, alias-based brute force, and nested query DoS. Use for GraphQL security testing, schema enumeration, or GraphQL API penetration testing.

The author's original description, preserved in English. It describes intent, not verified performance.

Performs GraphQL introspection attacks that extract the full API schema (types, queries, mutations, subscriptions, field definitions), map the attack surface, test query depth/complexity limits, and exploit GraphQL-specific weaknesses such as batching attacks, alias-based brute force, and nested query DoS. Use for GraphQL security testing, schema enumeration, or GraphQL API penetration testing.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Performs GraphQL introspection attacks that extract the full API schema (types, queries, mutations, subscriptions, field definitions), map the attack surface, test query depth/complexity limits, and exploit GraphQL-specific weaknesses such as batching attacks, alias-based brute force, and nested query DoS. Use for GraphQL security testing, schema enumeration, or GraphQL API penetration testing. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L56]
  • Step 1: GraphQL Endpoint Discovery [Source statement; provisional, not tested. Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L58]
  • Step 2: Full Introspection Query [Source statement; provisional, not tested. Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L98]
  • Step 3: Sensitive Data Identification in Schema [Source statement; provisional, not tested. Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L226]
  • Step 4: Schema Reconstruction When Introspection is Disabled [Source statement; provisional, not tested. Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L274]
  • Step 5: GraphQL Attack Techniques [Source statement; provisional, not tested. Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L320]
  • Step 6: Field-Level Authorization Testing [Source statement; provisional, not tested. Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L396]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L1-L31]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
39.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-graphql-introspection-attack/LICENSEOther11 KB
skills/performing-graphql-introspection-attack/references/api-reference.mdReference4.9 KB
skills/performing-graphql-introspection-attack/scripts/agent.pyScript4.5 KB
skills/performing-graphql-introspection-attack/SKILL.mdInstruction19.2 KB

SKILL.md frontmatter

{
  "name": "performing-graphql-introspection-attack",
  "description": "Performs GraphQL introspection attacks that extract the full API schema (types, queries, mutations, subscriptions, field definitions), map the attack surface, test query depth/complexity limits, and exploit GraphQL-specific weaknesses such as batching attacks, alias-based brute force, and nested query DoS. Use for GraphQL security testing, schema enumeration, or GraphQL API penetration testing.\n",
  "domain": "cybersecurity",
  "subdomain": "api-security",
  "tags": [
    "api-security",
    "graphql",
    "introspection",
    "schema-extraction",
    "query-abuse"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "ID.RA-01",
    "PR.DS-10",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1190",
    "T1059.007",
    "T1552.001",
    "T1110"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: GraphQL Endpoint Discovery

    Source-described action candidate under “Step 1: GraphQL Endpoint Discovery”; not verified execution.

  4. 04
    Action

    Step 2: Full Introspection Query

    Source-described action candidate under “Step 2: Full Introspection Query”; not verified execution.

  5. 05
    Action

    Step 3: Sensitive Data Identification in Schema

    Source-described action candidate under “Step 3: Sensitive Data Identification in Schema”; not verified execution.

  6. 06
    Action

    Step 4: Schema Reconstruction When Introspection is Disabled

    Source-described action candidate under “Step 4: Schema Reconstruction When Introspection is Disabled”; not verified execution.

Inspect all extracted workflow candidates (20 candidate steps)
  1. 07
    Action

    Step 5: GraphQL Attack Techniques

    Source-described action candidate under “Step 5: GraphQL Attack Techniques”; not verified execution.

  2. 08
    Action

    Step 6: Field-Level Authorization Testing

    Source-described action candidate under “Step 6: Field-Level Authorization Testing”; not verified execution.

  3. 09
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 10
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  5. 11
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  6. 12
    Action

    Run full introspection query against `/graphql` endpoint - complete schema extracted with 45 types, 120 queries, and 38 mutations

    Source-described action candidate under “Scenario: E-Commerce GraphQL API Security Assessment”; not verified execution.

  7. 13
    Action

    Identify sensitive types: `AdminUser`, `PaymentInfo`, `InternalConfig`, `AuditLog`

    Source-described action candidate under “Scenario: E-Commerce GraphQL API Security Assessment”; not verified execution.

  8. 14
    Action

    Discover that `User` type exposes `passwordHash`, `mfaSecret`, and `lastLoginIp` fields

    Source-described action candidate under “Scenario: E-Commerce GraphQL API Security Assessment”; not verified execution.

  9. 15
    Action

    Find admin mutations accessible to regular users: `deleteUser`, `updateRole`, `exportAllOrders`

    Source-described action candidate under “Scenario: E-Commerce GraphQL API Security Assessment”; not verified execution.

  10. 16
    Action

    Test query depth: no limit enforced, nested query 50 levels deep executes successfully and takes 45 seconds

    Source-described action candidate under “Scenario: E-Commerce GraphQL API Security Assessment”; not verified execution.

  11. 17
    Action

    Test alias batching: 1000 login attempts in a single request bypass rate limiting

    Source-described action candidate under “Scenario: E-Commerce GraphQL API Security Assessment”; not verified execution.

  12. 18
    Action

    Test batch queries: array of 500 queries accepted without limit

    Source-described action candidate under “Scenario: E-Commerce GraphQL API Security Assessment”; not verified execution.

  13. 19
    Action

    Schema reveals internal `InternalConfig` type with `databaseConnectionString` and `stripeSecretKey` fields

    Source-described action candidate under “Scenario: E-Commerce GraphQL API Security Assessment”; not verified execution.

  14. 20
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

29 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

20 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 20 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

6 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

3 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-graphql-introspection-attack/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/performing-graphql-introspection-attack/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-graphql-introspection-attack
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.