Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a real Pipedrive API helper, but it needs review because it can affect live CRM records while giving broad and inconsistent usage guidance.
Review before installing. Use only with a least-privileged or test Pipedrive/Maton credential, require explicit confirmation before any create, update, delete, or webhook operation, and avoid printing or pasting API keys into logs or shared transcripts.
The recovery example is malformed (urllib.request.maton.ai/connections')) and does not perform the documented verification step, while also contradicting the surrounding API usage guidance. Broken troubleshooting for authentication can cause users to misdiagnose failures, improvise unsafe fixes, or bypass expected validation when handling credentials and live API access.
The manifest claims managed OAuth support, but the usage example instructs users to send a raw MATON_API_KEY bearer token directly. This inconsistency can confuse the trust boundary and encourage use of broader static credentials where users expect delegated OAuth, increasing the chance of credential misuse or over-privileged access.
The skill is described with very broad productivity and workflow-optimization language, making it likely to be selected for generic requests beyond narrow Pipedrive tasks. In agent ecosystems, overbroad routing can cause the skill to receive unrelated sensitive data or trigger external API actions in contexts where the user did not clearly intend CRM access.
The FAQ and capability descriptions discuss creating, updating, deleting, and webhook-related operations against Pipedrive without prominent warnings that these affect live remote records. In this context, the skill has exec/write capability and targets a production CRM, so unclear safety boundaries increase the risk of unintended data modification, deletion, or operational changes.
No suspicious patterns detected.
