Security audit
Security checks for vulnerabilities and agentic risk
This is a straightforward scheduling API skill, but users should apply normal privacy and confirmation controls before sending attendee details or changing calendars.
Install only if you are comfortable sending scheduling details to the listed third-party paid gateway. Configure agents to get approval before booking or rescheduling important appointments, minimize sensitive notes, and notify affected attendees when changes are made.
The skill handles personally identifiable scheduling data such as names, emails, meeting times, and notes, but it provides no warning that this information will be transmitted to an external paid gateway. Users or downstream agents may send sensitive calendar and customer data without realizing the privacy, consent, and data-handling implications.
The use case explicitly describes automatically rescheduling missed appointments, but the skill does not warn that autonomous calendar modifications can create unintended bookings, customer confusion, or business disruption if triggered without confirmation. In scheduling contexts, silent changes to time-sensitive events can have real operational and privacy consequences.
