Security audit
Security checks for vulnerabilities and agentic risk
This Notion skill mostly matches its stated purpose, but it also asks for broad command execution and local file authority that are not clearly bounded to Notion tasks.
Install only if you are comfortable giving the agent Notion workspace mutation authority and broad local command capability. Use a least-privilege Notion integration shared only with the pages or databases needed, keep the token in an environment variable, and explicitly confirm any create, update, or delete action before it runs.
The skill presents command execution as a user-facing capability despite being a Notion API integration, which expands the attack surface far beyond the stated purpose. In an agent environment, normalizing exec without strict scoping can enable prompt-driven shell execution, unsafe local actions, or abuse of host access unrelated to Notion operations.
Declaring exec capability for a skill whose core purpose is interacting with the official Notion API grants unnecessary privileges. Excess capability is dangerous because an attacker can coerce the agent to perform local command execution or system access that is unrelated to the Notion workflow, increasing the blast radius of prompt injection or misuse.
The skill documents create, update, and delete operations against workspace data without prominently warning users that these actions are destructive or modifying. In an agent setting, unclear disclosure raises the risk of accidental data loss, unauthorized modifications, or users invoking dangerous actions without understanding the consequences.
No suspicious patterns detected.
