mollie-webhooks
Pass
Audited by Gen Agent Trust Hub on Oct 13, 2026
Risk Level: SAFEEXTERNAL_DOWNLOADSCOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [SAFE]: The skill focuses on the 'fetch-to-confirm' pattern, which is the industry-standard security model for Mollie webhooks. It provides clear warnings that webhook request bodies must not be trusted and demonstrates how to verify payment status by querying the official Mollie API using a server-side secret.
- [EXTERNAL_DOWNLOADS]: The documentation suggests using
hookdeck-clivianpxfor local development. This is an official utility provided by the skill's author (hookdeck) for webhook tunneling and does not constitute an unsafe remote download. - [COMMAND_EXECUTION]: The examples include standard instructions for setting up development environments using package managers like
npmandpip, as well as running local servers withuvicornandnode. - [INDIRECT_PROMPT_INJECTION]:
- Ingestion points: The webhook handlers ingest an
idparameter fromapplication/x-www-form-urlencodedpayloads (detected inmain.py,src/index.js, androute.ts). - Boundary markers: The skill's architecture implements a functional boundary where all data in the incoming request is ignored except for the ID, which is then used to perform an authenticated out-of-band request to the service provider.
- Capability inventory: The code samples utilize network access via
httpxor@mollie/api-clientto communicate withapi.mollie.com. - Sanitization: The
idis treated as a literal identifier for API lookups and is not executed or interpreted as a prompt. - [DATA_EXPOSURE]: The skill provides best-practice guidance for handling secrets, instructing users to store the
MOLLIE_API_KEYin environment variables rather than hardcoding it.
Audit Metadata