Security audit
Security checks for vulnerabilities and agentic risk
This is a simple yoga search and booking skill for Lokuli, with expected external booking data use but some consent and trigger-scope caveats.
Before installing, understand that booking through this skill may send your name, email, phone number, location or ZIP code, and selected time slot to Lokuli. Use it when you actually want Lokuli-powered yoga search or booking, and confirm the provider, time, and contact details before creating a booking.
The create_booking example shows transmission of customer name, email, and phone number to an external MCP endpoint, but the skill description does not warn that personal data will be sent off-platform. This is dangerous because users may provide sensitive contact information without informed consent, creating privacy, compliance, and trust risks if data is shared unexpectedly.
The trigger text is broad enough to activate on loosely related requests such as any yoga service request, which can cause the agent to invoke this skill when the user did not clearly ask to use Lokuli or make a booking. In a booking flow, over-triggering is risky because it can move a user from general information seeking into an external transaction context and may lead to unintended disclosure of location or booking details.
No suspicious patterns detected.
