prowler-mcp

Estrellas14.526

Forks2301

Actualizado16 de julio de 2026 a las 13:15

Creates MCP tools for Prowler MCP Server. Covers BaseTool pattern, model design, and API client usage. Trigger: When working in mcp_server/ on tools (BaseTool), models (MinimalSerializerMixin/from_api_response), or API client patterns.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

prowler-cloud

prowler-cloud/prowler

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

4 archivos

SKILL.md

readonly

name	prowler-mcp
description	Creates MCP tools for Prowler MCP Server. Covers BaseTool pattern, model design, and API client usage. Trigger: When working in mcp_server/ on tools (BaseTool), models (MinimalSerializerMixin/from_api_response), or API client patterns.
license	Apache-2.0
metadata	{"author":"prowler-cloud","version":"1.0","scope":["root","mcp_server"],"auto_invoke":"Working on MCP server tools"}
allowed-tools	Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task

Overview

The Prowler MCP Server uses three sub-servers with prefixed namespacing:

Sub-Server	Prefix	Auth	Purpose
Prowler	`prowler_*`	Required	Prowler Cloud, Private Cloud & Local Server management tools
Prowler Hub	`prowler_hub_*`	No	Security checks catalog
Prowler Docs	`prowler_docs_*`	No	Documentation search

For complete architecture, patterns, and examples, see docs/developer-guide/mcp-server.mdx.

Critical Rules (Prowler Tools Only)

Tool Implementation

ALWAYS: Extend BaseTool (auto-registered via tool_loader.py, only public methods from the class are exposed as a tool)
NEVER: Manually register BaseTool subclasses
NEVER: Import tools directly in server.py

Models

ALWAYS: Use MinimalSerializerMixin for responses
ALWAYS: Implement from_api_response() factory method
ALWAYS: Use two-tier models (Simplified for lists, Detailed for single items)
NEVER: Return raw API responses

API Client

ALWAYS: Use self.api_client singleton
ALWAYS: Use build_filter_params() for query parameters
NEVER: Create new httpx clients

Hub/Docs Tools

Use @mcp.tool() decorator directly—no BaseTool or models required.

Quick Reference: New Prowler Tool

Create tool class in prowler_app/tools/ extending BaseTool
Create models in prowler_app/models/ using MinimalSerializerMixin
Tools auto-register via tool_loader.py

QA Checklist (Prowler Tools)

Tool docstrings describe LLM-relevant behavior
Models use MinimalSerializerMixin
API responses transformed to simplified models
Error handling returns {"error": str, "status": "failed"}
Parameters use Field() with descriptions
No hardcoded secrets

Resources

Full Guide: docs/developer-guide/mcp-server.mdx
Templates: See assets/ for tool and model templates

Más de este repositorio

mismo repositorio

prowler-attack-paths-query

prowler-cloud/prowler

Creates Prowler Attack Paths openCypher queries using the Cartography schema as the source of truth for node labels, properties, and relationships. Covers Prowler-specific additions (Internet node, ProwlerFinding, internal isolation labels), $provider_uid scoping, and list-property item nodes with typed `HAS_*` edges that run efficiently on both Neo4j and Amazon Neptune sinks. Trigger: When creating or updating Attack Paths queries.

2026-07-2814.5k

prowler-compliance

prowler-cloud/prowler

Creates, syncs, audits and manages Prowler compliance frameworks end-to-end. Covers the two supported JSON schemas (universal multi-provider and legacy per-provider), the SDK model tree (legacy attribute classes, universal ComplianceFramework, ConfigRequirements guardrails), output formatters (legacy per-framework + universal data-driven), API/UI consumption, upstream sync workflows, and cloud-auditor check-mapping reviews. Trigger: When working with compliance frameworks (CIS, CIS Controls, NIST, PCI-DSS, SOC2, GDPR, ISO27001, ENS, MITRE ATT&CK, CCC, C5, CSA CCM, DORA, KISA ISMS-P, ASD Essential Eight, DISA STIG, CISA SCuBA, SecNumCloud, FedRAMP, HIPAA, NIS2, Prowler ThreatScore), creating a universal multi-provider framework, adding ConfigRequirements guardrails, syncing with upstream catalogs, auditing check-to-requirement mappings, adding output formatters, or fixing compliance JSON bugs (duplicate IDs, empty Version, wrong Section, stale check refs).

2026-07-2114.5k

framework-compliance-triage

prowler-cloud/prowler

Make a cloud account compliant with a security or industry framework using Prowler Cloud.

2026-07-1614.5k

prowler-changelog

prowler-cloud/prowler

Manages changelog entries for Prowler components following keepachangelog.com format. Trigger: When creating PRs, adding changelog entries, or working with any CHANGELOG.md file in ui/, api/, mcp_server/, or prowler/.

2026-07-1314.5k

prowler-ui

prowler-cloud/prowler

Prowler UI-specific patterns. For generic patterns, see: typescript, react-19, nextjs-16, tailwind-4. Trigger: When working inside ui/ on Prowler-specific conventions (shadcn, folder placement, actions/adapters, shared types/hooks/lib).

2026-07-0814.5k

prowler-test-api

prowler-cloud/prowler

Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).

2026-07-0814.5k

name	prowler-mcp
description	Creates MCP tools for Prowler MCP Server. Covers BaseTool pattern, model design, and API client usage. Trigger: When working in mcp_server/ on tools (BaseTool), models (MinimalSerializerMixin/from_api_response), or API client patterns.
license	Apache-2.0
metadata	{"author":"prowler-cloud","version":"1.0","scope":["root","mcp_server"],"auto_invoke":"Working on MCP server tools"}
allowed-tools	Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task

Overview

The Prowler MCP Server uses three sub-servers with prefixed namespacing:

Sub-Server	Prefix	Auth	Purpose
Prowler	`prowler_*`	Required	Prowler Cloud, Private Cloud & Local Server management tools
Prowler Hub	`prowler_hub_*`	No	Security checks catalog
Prowler Docs	`prowler_docs_*`	No	Documentation search

For complete architecture, patterns, and examples, see docs/developer-guide/mcp-server.mdx.

Critical Rules (Prowler Tools Only)

Tool Implementation

ALWAYS: Extend BaseTool (auto-registered via tool_loader.py, only public methods from the class are exposed as a tool)
NEVER: Manually register BaseTool subclasses
NEVER: Import tools directly in server.py

Models

ALWAYS: Use MinimalSerializerMixin for responses
ALWAYS: Implement from_api_response() factory method
ALWAYS: Use two-tier models (Simplified for lists, Detailed for single items)
NEVER: Return raw API responses

API Client

ALWAYS: Use self.api_client singleton
ALWAYS: Use build_filter_params() for query parameters
NEVER: Create new httpx clients

Hub/Docs Tools

Use @mcp.tool() decorator directly—no BaseTool or models required.

Quick Reference: New Prowler Tool

Create tool class in prowler_app/tools/ extending BaseTool
Create models in prowler_app/models/ using MinimalSerializerMixin
Tools auto-register via tool_loader.py

QA Checklist (Prowler Tools)

Tool docstrings describe LLM-relevant behavior
Models use MinimalSerializerMixin
API responses transformed to simplified models
Error handling returns {"error": str, "status": "failed"}
Parameters use Field() with descriptions
No hardcoded secrets

Resources

Full Guide: docs/developer-guide/mcp-server.mdx
Templates: See assets/ for tool and model templates