enum-grpc

Enumerate gRPC services and classify authentication requirements via reflection and descriptor analysis.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill enum-grpc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enum-grpc
Source: https://github.com/salmanabdurrahman/pi-pentest-agent/tree/main/skills/enum-grpc
Command: npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill enum-grpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of visibility into gRPC-based architectures by automating the discovery of services, methods, and authentication policies without resorting to intrusive or unauthorized probing.

Core Features & Use Cases

  • Service Discovery: Automatically identifies gRPC endpoints and maps method signatures via server reflection or descriptor analysis.
  • Security Posture Assessment: Classifies authentication requirements and detects plaintext transport or missing mTLS configurations.
  • Use Case: During a security assessment, use this skill to map the attack surface of a microservices backend, identifying which methods are exposed without authentication and verifying that sensitive endpoints are properly secured.

Quick Start

Use the enum-grpc skill to perform a passive discovery and authentication classification on the target gRPC endpoint at 192.168.1.50 port 50051.

Frequently Asked Questions about enum-grpc

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

FAQPage Schema
How do I enumerate gRPC services and map method signatures during a security assessment?

To enumerate gRPC services, you map method signatures via server reflection or descriptor analysis. This approach automates the discovery of exposed endpoints without resorting to intrusive or unauthorized active probing.

What is the best way to map the attack surface of a gRPC microservices backend?

Mapping a gRPC attack surface involves identifying exposed methods without authentication and verifying sensitive endpoints are secured. You achieve this by classifying authentication requirements through descriptor analysis.

Can I detect missing mTLS configurations and plaintext transport in gRPC endpoints?

Yes, you can detect missing mTLS configurations and plaintext transport in gRPC endpoints. This is accomplished by assessing the security posture and classifying the transport and authentication policies of the target services.

Does gRPC enumeration require authorization before performing service discovery?

Yes, gRPC enumeration requires strict adherence to authorization gates and scope validation before performing any active probing or service discovery. This ensures security assessments remain passive and authorized.

How does reflection work for identifying gRPC endpoints in a microservices architecture?

Server reflection works for identifying gRPC endpoints by allowing clients to query the server for its service descriptions. This enables automated mapping of method signatures without needing direct access to compiled protobuf descriptor files.

When should I not use active probing for gRPC service discovery?

You should avoid active probing for gRPC service discovery when strict authorization gates and scope validation are not established. Use passive descriptor analysis instead to maintain compliance and prevent unauthorized intrusive scanning.